Visible to Intel only — GUID: GUID-40BCB6B6-59C7-4EFE-B57D-876392D155BD
Legal Information
Getting Help and Support
Introducing the Intel® SDK for OpenCL™ Applications
What's New in This Release
Which Version of the Intel® SDK for OpenCL™ Applications Should I Use?
Intel® Code Builder for OpenCL™ API Plug-in for Microsoft Visual Studio*
Intel® Code Builder for OpenCL™ API Plug-in for Eclipse*
Debugging OpenCL™ Kernels on GPU
Intel® SDK for OpenCL™ Applications Standalone Version
OpenCL™ 2.1 Development Environment
Intel® FPGA Emulation Platform for OpenCL™ Getting Started Guide
Troubleshooting Intel® SDK for OpenCL™ Applications Issues
Configuring Microsoft Visual Studio* IDE
Converting an Existing Project into an OpenCL™ Project
OpenCL™ New Project Wizard
Building an OpenCL™ Project
Using OpenCL™ Build Properties
Selecting a Target OpenCL™ Device
Generating and Viewing Assembly Code
Generating and Viewing LLVM Code
Generating Intermediate Program Binaries with Intel® Code Builder for OpenCL™ API Plug-in
Configuring OpenCL™ Build Options
Visible to Intel only — GUID: GUID-40BCB6B6-59C7-4EFE-B57D-876392D155BD
Enabling Debugging in OpenCL™ Runtime
To enable debugging mode in the Intel® OpenCL™ Runtime for compiling OpenCL code using Intel® SDK for OpenCL™ Applications - Debugger plug-in for Microsoft Visual Studio* IDE, do the following:
- Add the -g flag to the build options string parameter in the clBuildProgram function.
Specify full path to the file in the build options string parameter to the clBuildProgram function accordingly (including the CL file name):
-s <full path to the OpenCL source file>
If the path includes spaces, enclose the entire path with double quotes.
For example:
err = clBuildProgram(
g_program,
0,
NULL,
"-g -s \"<path_to_opencl_source_file>\"",
NULL,
NULL);
NOTE:
Relative path to the CL file is not supported.
According to the OpenCL standard, work-items execute OpenCL kernels simultaneously. The Debugger requires setting the global ID of the work-item to debug before the debugging session starts. The Debugger stops on breakpoints in OpenCL code only when the pre-set work-item reaches them.
NOTE:
To work with the Intel SDK for OpenCL Applications - Debugger plug-in for Microsoft Visual Studio* IDE, the OpenCL kernel code must exist in a text file, separate from the code of the host. Debugging OpenCL code that appears only in a string embedded in the host application is not supported. Create your OpenCL project with the Intel® Code Builder for OpenCL™ API plug-in for Microsoft Visual Studio* to get seamless integration with the Debugger.