Developer Guide and Reference

Contents

qopenmp-lib, Qopenmp-lib

Lets you specify an OpenMP* run-time library to use for linking.

Syntax

Linux:
-qopenmp-lib=
type
macOS:
-qopenmp-lib=
type
Windows:
/Qopenmp-lib:
type
Arguments
type
Specifies the type of library to use; it implies compatibility levels. Currently, the only possible value is:
compat
Tells the compiler to use the compatibility OpenMP* run-time library (libiomp). This setting provides compatibility with object files created using Microsoft* and GNU* compilers.
Default
-qopenmp-lib=compat
or
/Qopenmp-lib:compat
The compiler uses the compatibility OpenMP* run-time library (libiomp).
Description
This option lets you specify an OpenMP* run-time library to use for linking.
The compatibility OpenMP run-time libraries are compatible with object files created using the Microsoft* OpenMP run-time library (vcomp) or the GNU OpenMP run-time library (libgomp).
To use the compatibility OpenMP run-time library, compile and link your application using the compat setting for option
[q or Q]openmp-lib
. To use this option, you must also specify one of the following compiler options:
  • Linux* systems:
    -qopenmp
    or
    -qopenmp-stubs
  • Windows* systems:
    /Qopenmp
    or
    /Qopenmp-stubs
On Windows* systems, the compatibility OpenMP* run-time library lets you combine OpenMP* object files compiled with the Microsoft* C/C++ compiler with OpenMP* object files compiled with the Intel® C, Intel® C++, or Intel® Fortran compilers. The linking phase results in a single, coherent copy of the run-time library.
On Linux* systems, the compatibility Intel OpenMP* run-time library lets you combine OpenMP* object files compiled with the GNU* gcc or gfortran compilers with similar OpenMP* object files compiled with the Intel® C, Intel® C++, or Intel® Fortran compilers. The linking phase results in a single, coherent copy of the run-time library.
The compatibility OpenMP run-time library is not compatible with object files created using versions of the Intel compilers earlier than 10.0.
On Windows* systems, this option is processed by the compiler, which adds directives to the compiled object file that are processed by the linker. On Linux*
and
macOS*
systems, this option is processed by the
icc/icpc
command that initiates linking, adding library names explicitly to the link command.
Alternate Options
None

Product and Performance Information

1

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804