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.
1698 Discussions

Few issue with data returned by clGetDeviceInfo()

Daniel_F_
Beginner
‎02-01-2017 11:16 PM
278 Views

I am playing with OpenCL Runtime 16.1.1 for Windows 64 bit and found that clGetDeviceInfo() returns some invalid data when quering my i7-2600K:

- query for CL_DEVICE_SINGLE_FP_CONFIG returned value 0x07 = CL_FP_DENORM | CL_FP_INF_NAN | CL_FP_ROUND_TO_NEAREST. Looks that CL_FP_ROUND_TO_ZERO and CL_FP_ROUND_TO_INF are missing. CL_FP_CORRECTLY_ROUNDED_DIVIDE_SQRT (new in OpenCL 1.2) is probably missing too.

- query for CL_DEVICE_DOUBLE_FP_CONFIG returned value 0x3F = CL_FP_DENORM | CL_FP_INF_NAN | CL_FP_ROUND_TO_NEAREST | CL_FP_ROUND_TO_ZERO | CL_FP_ROUND_TO_INF | CL_FP_FMA. i7-2600K does not support FMA3, so FMA flag look incorrect here.

- query for CL_DEVICE_BUILT_IN_KERNELS returned 0 in param_value_size_ret. My other OpenCL drivers (Nvidia, pocl) returns 1 when value is an empty string. This allows to allocate this many bytes of memory without extra checking if value is zero. Please check if your behavior is compliant with OpenCL standard.

0 Kudos

Link Copied

0 Replies
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.