Visible to Intel only — GUID: GUID-4AC3D696-F9A5-4064-A34A-A948300B80C7
Visible to Intel only — GUID: GUID-4AC3D696-F9A5-4064-A34A-A948300B80C7
qopenmp, Qopenmp
Enables recognition of OpenMP* features and tells the parallelizer to generate multi-threaded code based on OpenMP* directives.
Linux: |
-qopenmp -qno-openmp |
Windows: |
/Qopenmp /Qopenmp- |
None
-qno-openmp or /Qopenmp- |
No OpenMP* multi-threaded code is generated by the compiler. |
This option enables recognition of OpenMP* features and tells the parallelizer to generate multi-threaded code based on OpenMP* directives. The code can be executed in parallel on both uniprocessor and multiprocessor systems.
This option works with any optimization level. Specifying no optimization (-O0 on Linux* or /Od on Windows*) helps to debug OpenMP applications.
This option can also be specified as -fopenmp on Linux* systems.
To enable offloading to a specified GPU target, you must also specify option fopenmp-targets (Linux*) or /Qopenmp-targets (Windows).
Option -fopenmp is not the same as option -qopenmp. Option -fopenmp will not do offloading.
Options that use OpenMP* API are available for both Intel® microprocessors and non-Intel microprocessors, but these options may perform additional optimizations on Intel® microprocessors than they perform on non-Intel microprocessors. The list of major, user-visible OpenMP constructs and features that may perform differently on Intel® microprocessors versus non-Intel microprocessors include: locks (internal and user visible), the SINGLE construct, barriers (explicit and implicit), parallel loop scheduling, reductions, memory allocation, thread affinity, and binding.
Product and Performance Information |
---|
Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex. Notice revision #20201201 |
Visual Studio: Language > OpenMP* Support
Eclipse: Language > Process OpenMP Directives
Linux: -fiopenmp
Windows: /Qiopenmp