topic Could you please attach in OpenCL* for CPU

Compiler crash [15.1, Ubuntu]

Kloeckner__Andreas — Sat, 11 Apr 2015 20:15:25 GMT

The attached kernel crashes the Intel OpenCL Runtime 15.1 (Ubuntu):

Both operands to ICmp instruction are not of the same type!
  %37 = icmp slt i32 %35, i64 0
Both operands to a binary operator are not of the same type!
  %47 = add i32 %36, i64 1
Both operands to a binary operator are not of the same type!
  %48 = add i32 %47, i64 %24
Both operands to ICmp instruction are not of the same type!
  %51 = icmp slt i64 %44, i32 %50
Both operands to ICmp instruction are not of the same type!
  %52 = icmp slt i32 %50, i64 0
Invalid operands for select instruction!
  %54 = select i1 %53, i64 %44, i32 %50
Broken module found, compilation aborted!
Stack dump:
0.      Running pass 'Function Pass Manager' on module 'main'.
1.      Running pass 'Module Verifier' on function '@layerpot'
[1]    25966 abort      python -c

Here's a quick one-liner to reproduce the crash.

python -c 'import pyopencl as cl ; ctx = cl._csc(); cl.Program(ctx, open("qbx.cl.txt").read()).build()'

Could you please attach

Robert_I_Intel — Tue, 14 Apr 2015 04:26:21 GMT

Could you please attach pyopencl-complex.h file from your system as well?

Done.

Kloeckner__Andreas — Tue, 14 Apr 2015 04:48:23 GMT

Done.

Just verified that this works

Robert_I_Intel — Tue, 14 Apr 2015 20:23:19 GMT

Just verified that this works fine on Windows CPU OpenCL. Could you please provide your system details, e.g. you CPU, version of Ubuntu you are running, version of the OpenCL Code Builder you installed? It will help to file a bug with the product team. Thanks!

CPU: Intel(R) Core(TM) i7

Kloeckner__Andreas — Wed, 15 Apr 2015 03:55:51 GMT

CPU: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz

OS: Debian jessie (8.0) -- Ubuntu 14.10 is the most closely related version

I downloaded intel_code_builder_for_opencl_2015_ubuntu_5.0.0.43_x64.tgz

Hi,

Yuri_K_Intel — Wed, 15 Apr 2015 13:23:37 GMT

Hi, I was able to reproduce this issue on the version of OpenCL runtime that you mentioned, but it's not reproducible on our latest internal/development versions. So once new Intel OpenCL runtime release is available it should incorporate the fix for this issue. Thanks Yuri