Visible to Intel only — GUID: GUID-25251187-4A1E-4D82-9E50-F591EAD1C994
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
Creating and Launching a New Analyze Session
Analysis Results
Session Info
Host Profiling
Kernel Overview
Kernel Analysis
Host-Side Analysis Optimization Tips
Revising Code and Rerunning a Host Profiling Session
Revising Code and Rerunning a Kernel Profiling Session
See Also
Configuring the Code Analyzer
Visible to Intel only — GUID: GUID-25251187-4A1E-4D82-9E50-F591EAD1C994
Revising Code and Rerunning a Kernel Profiling Session
After you optimize your code, you can rerun the Code Analyzer session and compare the data to see how your changes improve your application performance in the Kernel Development Framework.
During the performance analysis run the code analyzer stored all the kernels that were executed during the analysis, together with their inputs, as a session of Kernel Development Framework.
To open this session in the Kernel Development Framework, click the Edit Kernel button in the Kernel Analysis page.
For each analysis session, the analysis tool creates a session directory named with the following information:
- application's name
- the date
- an incremented session number.
When you start profiling begins, and each time you pause and resume the data collection during the session, a new capture subdirectory is created in the session directory.
The capture directory is called capture and an incrementing number (for example, capture_1, capture_2). The capture directory includes capture reports in a binary format.
You can open this binary file in Visual Studio from the Analyze Sessions Explorer.
In addition, a session file is created in the session directory. This file stores the data about session configuration. You can use it to create and run another similar session. You can also export the analysis result to .html and .csv format.