topic clCreateProgramWithBinary segfault in OpenCL* for CPU

clCreateProgramWithBinary segfault

spiridonov__igor — Sun, 07 Oct 2018 16:42:55 GMT

Hello.

I get segfault on cpu device when I use clCreateProgramWithBinary with "enqueue_kernel" of opencl 2.0

Here is simple example - https://github.com/OmegaDoom/clCreateProgramWithBinary-segfault

If we change device to gpu then no segfault.

I have latest graphics driver - win64_24.20.100.6323

Intel® Core™ i7-7820HQ CPU @ 2.90GHz

Hi IgorS,

Michael_C_Intel1 — Tue, 16 Oct 2018 18:47:53 GMT

Hi IgorS,

Thanks for such an insightful issue report.

Which cpu implementation/device name/platform are you using?

Can you try Intel® CPU Runtime for OpenCL™ Applications 18.1 to use the CPU device? It debuted last week. At this point, any related changes would go into this implementation. This implementation replaces experimental cpu implementations included with the SDK and the 16.1.2 release.

See the Linux* OS and Windows* OS CPU downloads on this page: https://software.intel.com/en-us/articles/opencl-drivers

-MichaelC

Hi Michael.

spiridonov__igor — Wed, 17 Oct 2018 03:15:00 GMT

Hi Michael.

The problem still exists on driver 25.20.100.6326 (although it's good that qt is working now:)).

I wasn't precise. clCreateProgramWithBinary itself doesn't segfault. It's clEnqueueReadBuffer that throws but only with combination of clCreateProgramWithBinary.

I'm using first suitable intel platform - Intel(R) OpenCL and device - OpenCL 2.1 (Build 716)

Thanks for the reproducer. I

Michael_C_Intel1 — Fri, 09 Nov 2018 23:26:00 GMT

Thanks for the reproducer. I've created internal filing (reference #3724) w.r.t to this issue describing my findings for the dev team.

-MichaelC

Thank you Michael.

spiridonov__igor — Tue, 13 Nov 2018 13:21:34 GMT

Thank you Michael.

This problem arose when I tried to use pyopencl. By default it cashes kernels with clCreateProgramWithBinary similar to my example. it's possible to turn it off but better to fix this bug.