HOME
| OPENMP API Specification: Version 5.0 November 2018

3.1  Runtime Library Definitions

For each base language, a compliant implementation must supply a set of definitions for the OpenMP API runtime library routines and the special data types of their parameters. The set of definitions must contain a declaration for each OpenMP API runtime library routine and variable and a definition of each required data type listed below. In addition, each set of definitions may specify other implementation specific values.

SVG-Viewer needed.

The library routines are external functions with “C” linkage.

Prototypes for the C/C++ runtime library routines described in this chapter shall be provided in a header file named omp.h. This file also defines the following:

SVG-Viewer needed.

SVG-Viewer needed.

The omp.h header file also defines a class template that models the Allocator concept in the omp::allocator namespace for each predefined memory allocator in Table 2.10 on page 434 for which the name includes neither the omp_ prefix nor the _alloc suffix.

SVG-Viewer needed.

SVG-Viewer needed.

The OpenMP Fortran API runtime library routines are external procedures. The return values of these routines are of default kind, unless otherwise specified.

Interface declarations for the OpenMP Fortran runtime library routines described in this chapter shall be provided in the form of a Fortran include file named omp_lib.h or a Fortran 90 module named omp_lib. It is implementation defined whether the include file or the module file (or both) is provided.

These files also define the following:

It is implementation defined whether any of the OpenMP runtime library routines that take an argument are extended with a generic interface so arguments of different KIND type can be accommodated.

SVG-Viewer needed.