Visible to Intel only — GUID: GUID-026CEF11-6333-4967-8D25-276FD7CAC73F
Legal Information
Getting Help and Support
Introduction
Check-list for OpenCL™ Optimizations
Tips and Tricks for Kernel Development
Application-Level Optimizations
Debugging OpenCL™ Kernels on Linux* OS
Performance Debugging with Intel® SDK for OpenCL™ Applications
Coding for the Intel® Architecture Processors
Why Optimizing Kernels Is Important?
Avoid Spurious Operations in Kernels
Avoid Handling Edge Conditions in Kernels
Use the Preprocessor for Constants
Prefer (32-bit) Signed Integer Data Types
Prefer Row-Wise Data Accesses
Use Built-In Functions
Avoid Extracting Vector Components
Task-Parallel Programming Model Hints
Common Mistakes in OpenCL™ Applications
Introduction for OpenCL™ Coding on Intel® Architecture Processors
Vectorization Basics for Intel® Architecture Processors
Vectorization: SIMD Processing Within a Work Group
Benefitting from Implicit Vectorization
Vectorizer Knobs
Targeting a Different CPU Architecture
Using Vector Data Types
Writing Kernels to Directly Target the Intel® Architecture Processors
Work-Group Size Considerations
Threading: Achieving Work-Group Level Parallelism
Efficient Data Layout
Using the Blocking Technique
Intel® Turbo Boost Technology Support
Global Memory Size
Visible to Intel only — GUID: GUID-026CEF11-6333-4967-8D25-276FD7CAC73F
Debugging OpenCL™ Kernels on Linux* OS
The Intel® CPU Runtime for OpenCL™ Applications supports debugging OpenCL™ kernels using a GNU GDB* or a LLDB* Debugger on Linux* OS. It allows for debugging host code and OpenCL kernels in a single debug session.
- Enabling Debugging in OpenCL™ CPU Compiler and Runtime
- Start a Debugging Session
- Conditional Breakpoints on Work Items
See Also
- For more information on the GNU* Project Debugger, see https://www.gnu.org/software/gdb/
- For more information on the LLDB* Debugger, see https://lldb.llvm.org/lldb-gdb.html