OpenCL SDK EOL - What to do with existing OpenCL code?

[SailingDreams]

Hi

I read in this post that the OpenCL SDK is EOL. What replaces the SDK for OpenCL coding/debugging/development on Window 10 PCs? 

If the OneAPI is the replacement, does the OneAPI package include the tools to develop OpenCL on MSVC? 

I noticed that this page on the 2022 CPU Runtime for OpenCL has a references the Intel® SDK for OpenCL™ Applications 2019 page. for OpenCL™ developer tools. 

My goal is to benchmark some existing OpenCL on an Intel processor's integrated GPUs but unfortunately it's confusing on what development tools to use.  The CPU Runtime may be handy for debug, but I've got to build/deploy for the GPUs.

Thx

[Ben_A_Intel · Accepted solution]

Hello, it is only the Intel OpenCL SDK that is EOL.  The Intel OpenCL SDK was one provider of the tools and libraries and headers needed to build OpenCL applications.  Our OpenCL implementations themselves, that allow you to run an OpenCL application on the CPU or GPU, are not EOL.  Our CPU and GPU (and FPGA!) OpenCL implementations are still among the most feature-rich and well-supported OpenCL implementations.

https://github.com/intel/compute-runtime

https://www.intel.com/content/www/us/en/developer/articles/technical/intel-cpu-runtime-for-opencl-applications-with-sycl-support.html

The tools and libraries and headers that are needed to build OpenCL applications are now open-source, largely eliminating the need for vendor-specific OpenCL SDKs.  Of note, the Khronos-provided OpenCL SDK recently received a significant upgrade, and I'd encourage you to look at it if you haven't recently:

https://www.khronos.org/blog/your-opencl-developer-experience-just-got-upgraded

https://github.com/KhronosGroup/OpenCL-SDK

I have a few examples on my personal GitHub that demonstrate how to build OpenCL applications using open-source tools as well:

https://github.com/bashbaug/SimpleOpenCLSamples

Hope this helps!  -- Ben