Following the successful alpha and beta releases, which received your great feedback, we released today the gold version of the Intel OpenCL SDK 1.1 for the CPU on www.intel.com/go/opencl. This SDK is conformant with OpenCL 1.1 specification.
You are now able to use the Intel OpenCL SDK to create and distribute OpenCL based applications optimized for Intel Core and Intel Xeon processors
Please go to therelease notes and see which items that were reported in this forum are now fixed.
- Arnon Peleg
Intel OpenCL SDK Product Marketing Manager
The OpenCL SDK End User Licenec Agreement talks about redistributables, without explicitly saying there is one for OpenCL. I couldn't find anything obvious in the install on my PC either.
Small complaint about the Windows install: we really should not abort the SDK install if the host machine does not meet the OpenCL minimum spec. The reason is that one may be using the machine only for development, not testing (thinking about working on a laptop while on a flight, for example).I may not want to run the app, but I still want to be able to work on the code.
We stomp on whatever other OpenCL implementation may be installed (at least we stomp on nVidia, I haven't tried the Stream SDK yet to see where they install their libOpenCL.so).
This makes it impossible (at least using the default install options) to run Intel OpenCL and nVidia OpenCL side by side (as the nVidia driver puts its libOpenCL.so.* in /usr/lib64 -- on 64-bit systems, of course - same as we do, by default). Yes, I know I can override the installation root with rpm options, but this isn't commonly known, and even less known is the fact that once you install the Intel SDK you lose the ability to run OpenCL on an installed nVidia GPU.
Perhaps we should revisit where we install our libraries by default? They don't actually *need* to be in /usr/lib64; the RPM install could easily put them anywhere and update ldconfig so they can be found. This would prevent user frustration and confusion in these cases.
libOpenCL is the ICD module (http://www.khronos.org/registry/cl/extensions/khr/cl_khr_icd.txt), which is (should be) common to all vendors. So, it shouldn't matter which version of it you have, whatever version should be able to display all existing OpenCL platforms in the system. If the Intel one doesn't do so, please report it.
Should I open a Premier issue or report it here?
The reason I ask is that on Linux, I am seeing only one platform and vendor name -- NVIDIA Corporation -- when I run the code in section 6.4 of the User Guide. Is there something else I am missing in setting up the Intel SDK on Linux?