cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

koarl0815
Journeyman III

CL_DEVICE_TYPE_DEFAULT in Stream SDK v2.3

No CPUs found...

Hi guys,

I've just tested the new Stream SDK v2.3 (x86_64, Linux) with our upcoming ViennaCL v1.1.0 library and noticed that clGetDeviceIDs() with flag CL_DEVICE_TYPE_DEFAULT does not return any CPU devices, even if a suitable CPU is present. With older versions of the Stream SDK, CPUs were detected, see

http://forums.amd.com/forum/messageview.cfm?catid=328&threadid=142084

Is this new behavior intentional? Did I miss something?

Cheers,
Karli

0 Likes
4 Replies

Originally posted by: koarl0815 Hi guys,

 

I've just tested the new Stream SDK v2.3 (x86_64, Linux) with our upcoming ViennaCL v1.1.0 library and noticed that clGetDeviceIDs() with flag CL_DEVICE_TYPE_DEFAULT does not return any CPU devices, even if a suitable CPU is present. With older versions of the Stream SDK, CPUs were detected, see

 

http://forums.amd.com/forum/messageview.cfm?catid=328&threadid=142084

 

Is this new behavior intentional? Did I miss something?



Default device is now the GPU.  Do you have a GPU present?  If you have no GPU and are still getting 0 devices, then that might be an issue.

Jeff

0 Likes

Hi,

sorry, seems like I haven't been precise enough. I've tested the behavior on several machines where only suitable CPUs are available, no GPUs. With CL_DEVICE_TYPE_DEFAULT no devices are 'found' and a CL_DEVICE_NOT_FOUND error is returned. However, the CPUs are returned when using CL_DEVICE_TYPE_CPU. Older versions of the Stream SDK work as expected, the issue shows up with v2.3 only.

Cheers,
Karli

0 Likes

This has been fixed internally.  Thanks for pointing it out.

Jeff

0 Likes

Hi,

you're welcome. 🙂
In the meanwhile I'll use (CL_DEVICE_TYPE_GPU | CL_DEVICE_TYPE_CPU).

Best regards,
Karli

0 Likes