Also export ICXCC, ICXCXX, ICXCPP, ICXLD, ICXAR in SDK environment which can
then be used to compile applications.
For example, to build an sample SYCL application using SDK:
-> Source oneAPI compiler setup script (from your installed path):
$ source /your-sdk-path/oecore-x86_64/sysroots/skylake-64-oe-linux/opt/intel/oneapi/compiler/2022.1.0/env/vars.sh
-> Build sample SYCL app (i.e simple-sycl-app.cpp):
$ $ICXCXX -fsycl simple-sycl-app.cpp -o simple-sycl-app -lsvml -lirng -limf -lintlc
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Support for Intel(R) oneAPI DPC++/C++ (icx) compiler is being added. So
remove the support for the classic compiler.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
The Intel® oneAPI DPC++/C++ Compiler provides optimizations
that help your applications run faster on Intel® 64 architectures with support
for the latest C, C++, and SYCL language standards. This compiler produces
optimized code that can run significantly faster by taking advantage of the
ever-increasing core count and vector register width in Intel® Xeon® processors
and compatible processors.
https://www.intel.com/content/www/us/en/developer/tools/oneapi/dpc-compiler.html
The compiler binaries are installed in /opt and can be invoked to compile
on target or using the SDK.
Currently dpcpp icx identify only x86_64-oe-linux triple, so it should be tested
with 'nodistro' DISTRO.
DISTRO ?= "nodistro"
To run SYCL program, it has dependencies on OpenCL components.
IMAGE_INSTALL:append = " intel-compute-runtime intel-graphics-compiler clang"
To install icx toolchain and runtime libraries
IMAGE_INSTALL:append = " intel-oneapi-dpcpp-cpp-runtime intel-oneapi-dpcpp-cpp-runtime-dev "
IMAGE_INSTALL:append = " intel-oneapi-dpcpp-cpp intel-oneapi-dpcpp-cpp-dev "
Once image is built and boots, an env script needs to be run to setup compiler environment and
also required to create dynamic linker symlink at /lib64
$ source /opt/intel/oneapi/compiler/2022.1.0/env/vars.sh
$ mkdir -p /lib64
$ ln -sf /lib/ld-linux-x86-64.so.2 /lib64/ld-linux-x86-64.so.2
To build an SYCL sample application, following command should be used
$ icpx --target=x86_64-oe-linux -fsycl simple-sycl-app.c -o simple-sycl-app
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
This recipe is not requried anymore, as already recipes for
mainline-tracking 5.19 kernel being added.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Build 5.19 RT kernel version from mainline-tracking tree at:
https://github.com/intel/mainline-tracking
This will track the mainline kernel and will be used to enable support for newer platforms.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Build 5.19 kernel version from mainline-tracking tree at:
https://github.com/intel/mainline-tracking
This will track the mainline kernel and will be used to enable support for newer platforms.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Include a patch from linux-yocto to fix buildpaths problem when
compiling perf. Fixes:
| WARNING: perf-1.0-r9 do_package_qa: QA Issue: File /usr/lib/python3.10/site-packages/perf-0.1-py3.10-linux-x86_64.egg/EGG-INFO/SOURCES.txt in package perf-python contains reference to TMPDIR
| File /usr/lib/python3.10/site-packages/perf-0.1-py3.10-linux-x86_64.egg/__pycache__/perf.cpython-310.pyc in package perf-python contains reference to TMPDIR [buildpaths]
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Build opencl-clang with llvm-15 and point to latest from ocl-open-150
branch.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
- Change gflag to shared as we are not building with static library.
- We are using zlib from yocto recipe, so don't add zlib as third party package
- Third party package mkl-dnn name changed to onednn upstream in openvino repo so changed
the name accordingly in openvino-inference-engine recipe
- Refresh patches
Release Notes:
https://github.com/openvinotoolkit/openvino/releases/tag/2022.2.0
Signed-off-by: Yogesh Tyagi <yogesh.tyagi@intel.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Also export ICC, ICCCXX, ICCCPP, ICCLD, ICCAR in SDK environment which can
then be used to compile applications in SDK
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Using the Intel® C++ Compiler Classic, you can compile and generate
applications that can run on Intel® 64 architecture.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
This is due to recent packaging chagnes in meta-clang
3d56a85afe
Error log:
do_package_qa: QA Issue: /usr/bin/ispc contained in package ispc
requires libclang-cpp.so.15()(64bit), but no providers found
in RDEPENDS:ispc? [file-rdeps]
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Upstream has force pushed master and the commit we were fetching is
no longer present on that branch. Remove the branch parameter and switch
to using nobranch to continue using that commit.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
