Developer Guide for Intel® SDK for OpenCL™ Applications 2017
A newer version of this document is available. Customers should click here to go to the newest version.
Visible to Intel only — GUID: GUID-CA7C98F8-8B4C-4FD7-B33F-D6B2400D8151
Visible to Intel only — GUID: GUID-CA7C98F8-8B4C-4FD7-B33F-D6B2400D8151
Configuring the API Debugger
You can configure several features of the Intel® SDK for OpenCL™ Applications - API Debugger, go to Tools > Intel Code Builder for OpenCL API > OpenCL API Debugger > Options to open the Code Builder - Debugger Configuration dialog box, and select the API Debugger tab:
| To do this... | Do this: |
|---|---|
| Configure the number of states to save per each memory object (Image, Buffers and SubBuffers). | In the Number of previous states field, set the appropriate number of states. |
| Enable raw data tracing. | Check the Enable Raw Data Tracing box. Note that this feature may cause performance degradation. |
| Dump image bitmaps. | Check the Enable Image Bitmap Tracing box. Note that this feature may cause performance degradation. |
| Enable automatic memory tracing. | In the Other settings group, check the Auto-generate session box. This option creates a separate directory for each captured session of the plug-in. The directory is stored under the Output Folder specified in the same window. |
| Configure the data buffering size. | In the Data buffering size (bytes) field, enter the appropriate number of bytes for the data buffer. Note that when debugging memory-bound applications, you many need to reduce the size of the buffer. |
| Set a custom port for API debugging. | Check the Use Custom Port box and set the appropriate port number in the text field. |
And can be enabled via:
Tools > Intel Code Builder for OpenCL API > OpenCL API Debugger > Options to open the Code Builder - Debugger Configuration dialog box, and select the API Debugger tab Other settings > Auto-generate session
Notes
-
NOTE:Profiling performance measured by either clGetEventProfilingInfo runtime API call or any other method for measuring execution time or occupied host memory, may cause performance degradation.
-
NOTE:To get more accurate profiling results, use the runtime directly via Ctrl+F5, Start w/o Debugging, or disabling API Debugger in the plug-in configuration menu.
- Only 2D images are supported for viewing, which is memory objects that contain CL_MEM_OBJECT_IMAGE2D in their image_type field inside their descriptor (cl_image_desc).
- Images above 2GB are not supported and are not be displayed
The bitmaps shown in the Image View are merely an 8-bit RGBA approximation of the underlying pixel array of the associated images.
NOTE:Behind the scenes, the plug-in does a liner color conversion from the input range of the pixels, which can be any type supported by the OpenCL runtime, for example, CL_SNORM_INT8, CL_UNSIGNED_INT16, and so on) to the [0..255] range.As a result, the presented colors might not accurately represent the bitmap as expected.