openmp Loop parallelism in OpenMP
Parameters
| Clause | Parameter |
|---|---|
private | Comma-separated list of private variables |
firstprivate | Like private, but initialized to the value of the variable before entering the loop |
lastprivate | Like private, but the variable will get the value corresponding to the last iteration of the loop upon exit |
reduction | reduction operator : comma-separated list of corresponding reduction variables |
schedule | static, dynamic, guided, auto or runtime with an optional chunk size after a coma for the 3 former |
collapse | Number of perfectly nested loops to collapse and parallelize together |
ordered | Tells that some parts of the loop will need to be kept in-order (these parts will be specifically identified with some ordered clauses inside the loop body) |
nowait | Remove the implicit barrier existing by default at the end of the loop construct |
Remarks
The meaning of the schedule clause is as follows:
static[,chunk]: Distribute statically (meaning that the distribution is done before entering the loop) the loop iterations in batched ofchunksize in a round-robin fashion. Ifchunkisn't specified, then the chunks are as even as possible and each thread gets at most one of them.dynamic[,chunk]: Distribute the loop iterations among the threads by batches ofchunksize with a first-come-first-served policy, until no batch remains. If not specified,chunkis set to 1guided[,chunk]: Likedynamicbut with batches which sizes get smaller and smaller, down to 1auto: Let the compiler and/or run time library decide what is best suitedruntime: Deffer the decision at run time by mean of theOMP_SCHEDULEenvironment variable. If at run time the environment variable is not defined, the default scheduling will be used
The default for schedule is implementation define. On many environments it is static, but can also be dynamic or could very well be auto. Therefore, be careful that your implementation doesn't implicitly rely on it without explicitly setting it.
In the above examples, we used the fused form parallel for or parallel do. However, the loop construct can be used without fusing it with the parallel directive, in the form of a #pragma omp for [...] or !$omp do [...] standalone directive within a parallel region.
For the Fortran version only, the loop index variable(s) of the parallized loop(s) is (are) always private by default. There is therefore no need of explicitly declaring them private (although doing so isn't a error).
For the C and C++ version, the loop indexes are just like any other variables. Therefore, if their scope extends outside of the parallelized loop(s) (meaning if they are not declared like for ( int i = ...) but rather like int i; ... for ( i = ... ) then they have to be declared private.
