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

Problem with kernel analysis with code builder in VS 2015

arvjo
Beginner
‎03-07-2017 01:29 AM
675 Views

Hi im having a problem with the deep kernel analysis of the openCL application analysis in the code builder plugin for visual studio 2015.

The host profiling and the kernel overview works fine but the kernel overview graphical view and the execution units, ticks per thread and threads per time only gives a error message:

Error: Unable to retrieve "Execution Units"

Error: Unable to retrieve "Times per thread"

Error: Unable to retrieve "Threads per time"

The latency part of the kernel analysis does not work either it only states: No records available.

Im running the application on an i7-4790 CPU and its integrated HD graphics 4600.

Does anyone know what could be causing this?

 

0 Kudos

Link Copied

1 Reply
Jeffrey_M_Intel1
Employee
‎03-07-2017 04:45 PM
675 Views

Official support for Intel SDK for OpenCL Applications 2016 R3 covers 5th, 6th, and 7th Generation Core processors.  For 4th Generation, the release notes indicate CPU only.  

This indicates what is validated, not necessarily that there is a technical block. I have also seen behavior like this cleared up by re-installing the SDK.

 

 

 

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. 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.