Intel® CPU Runtime for OpenCL™ Applications with SYCL support

ID 659639
Updated 7/20/2023
Version Latest



This page contains the experimental Intel® OpenCL CPU runtime libraries with SYCL support targeting machines with Intel® Xeon® Processor or Intel® Core™ Processor. 

Supported Operating Systems 

Please refer to the corresponding Release Notes on Intel® CPU Runtime for OpenCL™ Applications Release Notes.

Downloading the Intel® CPU Runtime for OpenCL™ Applications

Please download the required version of runtime library for your system:

Version 2023.2 release
Windows* download

For both IA-32 and Intel® 64 application: download the installable file w_opencl_runtime_p_2023.2.0.49500.exe and double click to install the runtime. 

Linux* download 

The runtime package for Linux* is distributed through APT and YUM.

Please follow the instructions on Install Using Package Managers to setup the reporsitory and install the package "intel-oneapi-runtime-opencl".

Notes for Windows Users 

Administrative permission is required to install theOpenCL CPU runtime on Windows. The installation will check the existing version of OpenCL CPU runtime, it only installs if the existing version is older than the downloaded version; otherwise it provides "Repair" and "Remove" functionalities. 

The OpenCL CPU runtimes will be installed to the following directory: 

  • C:\Program Files (x86)\Common Files\Intel\Shared Libraries\

Known Issues and Limitations 

  1. A known-issue in the installer of previous version of Intel® OpenCL driver for Intel® Graphics for Windows that removes one registray key, so the OpenCL application will fail to run on Intel CPU processor.
    1. Workaround: this issue can be fixed with the method below.
      1. Manually update the registry key: 
        1. run "Registry Editor" program
        2. go to HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors
        3. add a new key with following key-value pair: 
          "C:\\Program Files (x86)\\Common Files\\Intel\\Shared Libraries\\intelocl64.dll"=dword:0
    2. This issue has been fixed in the 2021.1 release.