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

Work Items Do Not Set Output on HD5500 GPU

Salvatore_D_
Beginner
‎07-19-2016 10:57 AM
490 Views

I'm having a problem with a few of my kernels on an i3-5010U CPU when running on the GPU device. When I specify an X offset of 2 or greater when queuing a kernel, every 16th row does not get calculated. I have a test project attached in a zip file. Visual Studio 2012 with the Intel OpenCL SDK integration is needed. The extension Image Watch is useful to visualize the problem. This issue is only seen when using the GPU device. I cannot reproduce using HD4400(Gen4) or HD520(Gen6) GPUs.

My configuration is:

  • Intel i3-5010U
  • Windows 7 Embedded
  • Graphics driver version 20.19.15.4454

Any help would be appreciated. I have found a workaround, but my code is correct as far as I can tell and I would like to not put fixes in when I don't understand the cause of the problem.

0 Kudos

Link Copied

2 Replies
Salvatore_D_
Beginner
‎07-19-2016 10:59 AM
490 Views

I forgot to attach the zip file. Here it is.

Gen5NucBug.zip
0 Kudos
Copy link
Jeffrey_M_Intel1
Employee
‎07-19-2016 03:13 PM
490 Views

Thanks for your description and reproducer.  I'll take a look and get back to you soon.

0 Kudos
Copy link
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.