OpenCL* for CPU
Ask questions and share information on Intel® SDK for OpenCL™ Applications and OpenCL™ implementations for Intel® CPU.
Announcements
This forum covers OpenCL* for CPU only. OpenCL* for GPU questions can be asked in the GPU Compute Software forum. Intel® FPGA SDK for OpenCL™ questions can be ask in the FPGA Intel® High Level Design forum.
1719 Discussions

OpenCL 18.1 CPU Runtime Sha1

Davis__James
Beginner
‎07-23-2019 05:54 AM
1,135 Views
Hello, I'm in the process of setting up the OpenCL 18.1 CPU Runtime on Linux. However, I noticed that the SHA1 of the file I downloaded form the Intel registration center (FileName l_opencl_p_18.1.0.015.tgz, Build Date May 07 2019) has a SHA1 of 5f2fa6e6bc400ca04219679f89ec289f17e94e5d. This is in contrast to the OpenCL Runtime page at https://software.intel.com/en-us/articles/opencl-drivers which reports the SHA1 should be 31509737eecf1657fe766318307c7a8f7f676beb. I suspect that the webpage was simply not updated after a new build, but would it be possible to confirm what the correct SHA1 should be? Many Thanks.
0 Kudos

Link Copied

1 Reply
Michael_C_Intel1
Moderator
‎07-23-2019 02:42 PM
1,135 Views

Hi JamesD,

 

Thanks for the question and the interest. I have updated that page to reflect the correct hashes.

SHA1 of 5f2fa6e6bc400ca04219679f89ec289f17e94e5d is correct. We had a maintenence update (same featureset, same version) so the packaging changed.

 

-MichaelC

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.