OpenMP 5.0 Features Not Covered for C/C++

[andrewkallai]

Taken from Version 4.5 to 5.0 Differences Section of the 5.0 Specification

• Iterators (see Section 2.1.6 on page 47) were added to support expressions in a list that expand to multiple expressions.
• The relational-op in the canonical loop form for C/C++ was extended to include != (see Section 2.9.1 on page 95).
• The default loop schedule modifier for worksharing-loop constructs without the static schedule and the ordered clause was changed to nonmonotonic (see Section 2.9.2 on page 101).
• The taskloop construct (see Section 2.10.2 on page 140) was added to the list of constructs that can be canceled by the cancel construct (see Section 2.18.1 on page 263)).
• The to and from clauses on the target update construct (see Section 2.12.6 on page 176), the depend clause on task generating constructs (see Section 2.17.11 on page 255), and the map clause (see Section 2.19.7.1 on page 315) were extended to allow any lvalue expression as a list item for C/C++.
• To support conditional assignment to lastprivate variables, the conditional modifier was added to the lastprivate clause (see Section 2.19.4.5 on page 288).
• The description of the map clause was modified to clarify the mapping order when multiple map-types are specified for a variable or structure members of a variable on the same construct. The close map-type-modifier was added as a hint for the runtime to allocate memory close to the target device (see Section 2.19.7.1 on page 315).
• The capability to map C/C++ pointer variables and to assign the address of device memory that is mapped by an array section to them was added. Support for mapping of Fortran pointer and allocatable variables, including pointer and allocatable components of variables, was added (see Section 2.19.7.1 on page 315).
• Runtime routines omp_set_affinity_format (see Section 3.2.30 on page 364), omp_get_affinity_format (see Section 3.2.31 on page 366), omp_set_affinity (see Section 3.2.32 on page 367), and omp_capture_affinity (see Section 3.2.33 on page 368) and environment variables OMP_DISPLAY_AFFINITY (see Section 6.13 on page 612) and OMP_AFFINITY_FORMAT (see Section 6.14 on page 613) were added to provide OpenMP runtime thread affinity information.
• The omp_pause_resource and omp_pause_resource_all runtime routines were added to allow the runtime to relinquish resources used by OpenMP (see Section 3.2.43 on page 378 and Section 3.2.44 on page 380).