Intel® Fortran supports OpenMP* Fortran compiler directives that comply with OpenMP Fortran Application Program Interface (API) specification Version TR4: Version 5.0.
To use these directives, you must specify compiler option -qopenmp (Linux* and macOS*) or /Qopenmp (Windows*).
OpenMP directives are specially formatted Fortran comment lines embedded in the source file which provide the compiler with hints and suggestions for parallelization, optimization, vectorization, and offloading code to accelerator hardware. The compiler uses the information specified in the directives with compiler heuristic algorithms to generate more efficient code. At times, these heuristics may choose to ignore or override the information provided by a directive. If the directive is ignored by the compiler, no diagnostic message is issued.
Options that use OpenMP* 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 vs. non-Intel microprocessors includes: locks (internal and user visible), the SINGLE construct, barriers (explicit and implicit), parallel loop scheduling, reductions, memory allocation, thread affinity, and binding.
This section discusses clauses used in multiple OpenMP* Fortran directives, conditional compilation rules, nesting and binding rules, and the following directives:
Specifies memory allocators to use for object allocation and deallocation. This feature is only available for ifx.
Specifies that a specific memory location is to be updated atomically.
Synchronizes all the threads in a team.
Requests cancellation of the innermost enclosing region of the type specified, and causes the encountering implicit or explicit task to proceed to the end of the canceled construct.
Defines a point at which implicit or explicit tasks check to see if cancellation has been requested for the innermost enclosing region of the type specified.
Restricts access for a block of code to only one thread at a time.
Declares a user-defined reduction for one or more types.
Generates a SIMD procedure.
Causes the creation of a device-specific version of a named routine that can be called from a target region.
Identifies a variant of a base procedure and specifies the context in which this variant is used. This feature is only available for ifx.
DISTRIBUTE directive construct
Specifies that loop iterations will be executed by thread teams in the context of their implicit tasks.
DISTRIBUTE PARALLEL DO directive construct
Specifies a loop that can be executed in parallel by multiple threads that are members of multiple teams.
DISTRIBUTE PARALLEL DO SIMD directive construct
Specifies a loop that will be executed in parallel by multiple threads that are members of multiple teams. It will be executed concurrently using SIMD instructions.
Specifies a loop that will be distributed across the master threads of the teams region. It will be executed concurrently using SIMD instructions.
Specifies that the iterations of the immediately following DO loop must be executed in parallel.
Specifies a loop that can be executed concurrently using SIMD instructions.
Specifies synchronization points where the threads in a team must have a consistent view of memory.
Specifies that the iterations of the associated loops can execute concurrently. This feature is only available for ifx.
Specifies a block of code to be executed by the master thread of the team.
Specifies a block of code that the threads in a team must execute in the natural order of the loop iterations.
Defines a parallel region.
PARALLEL DO directive construct
Defines a parallel region that contains a single DO directive.
PARALLEL DO SIMD directive construct
Specifies a loop that can be executed concurrently using SIMD instructions. It provides a shortcut for specifying a PARALLEL construct containing one SIMD loop construct and no other statement.
PARALLEL LOOP directive construct
Specifies a shortcut for indicating that a loop or loop nest can execute concurrently across multiple threads. This feature is only available for ifx.
PARALLEL SECTIONS directive construct
Defines a parallel region that contains a single SECTIONS directive.
PARALLEL WORKSHARE directive construct
Defines a parallel region that contains a single WORKSHARE directive.
Specifies a scan computation that updates each list item in each iteration of the loop the directive appears in.
Specifies that the enclosed SECTION directives define blocks of code to be divided among threads in a team.
Requires and controls SIMD vectorization of loops.
Specifies a block of code to be executed by only one thread in a team at a time.
Creates a device data environment and executes the construct on the same device.
TARGET DATA directive construct
Creates a device data environment for the extent of the region.
Specifies that variables are mapped to a device data environment.
Specifies that variables are unmapped from a device data environment.
TARGET PARALLEL directive construct
Creates a device data environment in a parallel region and executes the construct on that device.
TARGET PARALLEL DO directive construct
Provides an abbreviated way to specify a TARGET directive containing a PARALLEL DO directive and no other statements.
TARGET PARALLEL DO SIMD directive construct
Specifies a TARGET construct that contains a PARALLEL DO SIMD construct and no other statement.
TARGET PARALLEL LOOP directive construct
Specifies a shortcut for specifying a parallel loop inside a TARGET construct that contains no other statements than the parallel loop. This feature is only available for ifx.
TARGET SIMD directive construct
Specifies a TARGET construct that contains a SIMD construct and no other statement.
TARGET TEAMS directive construct
Creates a device data environment and executes the construct on the same device. It also creates a league of thread teams with the master thread in each team executing the structured block.
TARGET TEAMS DISTRIBUTE directive construct
Creates a device data environment and executes the construct on the same device. It also specifies that loop iterations will be shared among the master threads of all thread teams in a league created by a TEAMS construct.
TARGET TEAMS DISTRIBUTE PARALLEL DO directive construct
Creates a device data environment and then executes the construct on that device. It also specifies a loop that can be executed in parallel by multiple threads that are members of multiple teams created by a TEAMS construct.
TARGET TEAMS DISTRIBUTE PARALLEL DO SIMD directive construct
Creates a device data environment and then executes the construct on that device. It also specifies a loop that can be executed in parallel by multiple threads that are members of multiple teams created by a TEAMS construct. The loop will be distributed across the teams, which will be executed concurrently using SIMD instructions.
TARGET TEAMS DISTRIBUTE SIMD directive construct
Creates a device data environment and executes the construct on the same device. It also specifies that loop iterations will be shared among the master threads of all thread teams in a league created by a teams construct. It will be executed concurrently using SIMD instructions.
TARGET TEAMS LOOP directive construct
Specifies a shortcut for specifying a TEAMS LOOP construct inside a TEAMS construct that contains no other statements. This feature is only available for ifx.
Makes the list items in the device data environment consistent with their corresponding original list items.
Defines a task region.
Specifies a wait for the completion of all child tasks of the current task and all of their descendant tasks.
Specifies that the iterations of one or more associated DO loops should be executed in parallel using OpenMP* tasks. The iterations are distributed across tasks that are created by the construct and scheduled to be executed.
Specifies a loop that can be executed concurrently using SIMD instructions and that those iterations will also be executed in parallel using OpenMP* tasks.
Specifies a wait on the completion of child tasks generated since the beginning of the current task.
Specifies that the current task can be suspended at this point in favor of execution of a different task.
Creates a group of thread teams to be used in a parallel region.
TEAMS DISTRIBUTE directive construct
Creates a league of thread teams to execute a structured block in the master thread of each team. It also specifies that loop iterations will be shared among the master threads of all thread teams in a league created by a TEAMS construct.
TEAMS DISTRIBUTE PARALLEL DO directive construct
Creates a league of thread teams to execute a structured block in the master thread of each team. It also specifies a loop that can be executed in parallel by multiple threads that are members of multiple teams.
TEAMS DISTRIBUTE PARALLEL DO SIMD directive construct
Creates a league of thread teams to execute a structured block in the master thread of each team. It also specifies a loop that can be executed in parallel by multiple threads that are members of multiple teams. The loop will be distributed across the master threads of the teams region, which will be executed concurrently using SIMD instructions.
TEAMS DISTRIBUTE SIMD directive construct
Creates a league of thread teams to execute the structured block in the master thread of each team. It also specifies a loop that will be distributed across the master threads of the teams region. The loop will be executed concurrently using SIMD instructions.
TEAMS LOOP directive construct
Specifies a shortcut for specifying a LOOP construct inside a TEAMS construct. This feature is only available for ifx.
Makes named common blocks private to each thread, but global within the thread.
Divides the work of executing a block of statements or constructs into separate units.
The OpenMP parallel directives can be grouped into the categories. For more information about the categories for these directives, see OpenMP* Directives Summary.
Product and Performance Information |
---|
Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex. Notice revision #20201201 |
The OpenMP web site http://www.openmp.org/