OpenCL-Wrapper Hangs on Intel

Hi,

Is it normal and expected that the EXE hangs on Intel i3 Sandy Bridge? It shows nothing after the banner and pins the CPU at 100%. It also crashes on i7 Sandy Bridge.

Jul 14 '24 14:07 dca00

Hi @dca00,

that should not happen. Is that with the Intel CPU Runtime for OpenCL, or with PoCL? Can you please share the full console output up to the point where it hangs, for both CPUs?

Kind regards, Moritz

Jul 14 '24 21:07 ProjectPhysX

wrapper_2120

It sits like this for some time, then I kill it with Ctrl-C. Maybe I do not wait long enough. How long is it supposed to take?

Jul 15 '24 20:07 dca00

What seems to happen here is that the OpenCL Runtime compiler gets stuck.

Did you install the Intel CPU Runtime for OpenCL yourself on the system? This looks like an ancient version. Try with latest version.

Jul 16 '24 21:07 ProjectPhysX

Updated the runtime. Now, this is the output: Other than the output and that the CPU is pinned to 37%, the behavior hasn't changed.

Jul 17 '24 12:07 dca00

Ok you have the CPU showing up 3 times now, lets get to the bottom of it. By default Device ID 1 is selected. Try manually selecting Device ID 2. For this, change this line in src/main.cppto:

	Device device(select_device_with_id(2));

and compile+run it and post the output here. Try also with ID 0.

Jul 17 '24 17:07 ProjectPhysX

First, this message shows: And then: And then I can kill it with Ctrl-C

Jul 18 '24 21:07 dca00

This is the full expected output. The OpenCL kernel runs correctly.

To fix this weird error, try uninstalling the old version of the OpenCL CPU Runtime you have installed (twice?) to get rid of broken device ID listings 0 and 1.

Jul 19 '24 04:07 ProjectPhysX

It wasn't installed twice: the machine was reimaged clean and new runtime installed.

Jul 19 '24 10:07 dca00