141d390dcb
The parser will accept a wide variety of illegal attempts at forming an ATOMIC construct, leaving it to the semantic analysis to diagnose any issues. This consolidates the analysis into one place and allows us to produce more informative diagnostics. The parser's outcome will be parser::OpenMPAtomicConstruct object holding the directive, parser::Body, and an optional end-directive. The prior variety of OmpAtomicXyz classes, as well as OmpAtomicClause have been removed. READ, WRITE, etc. are now proper clauses. The semantic analysis consistently operates on "evaluation" representations, mainly evaluate::Expr (as SomeExpr) and evaluate::Assignment. The results of the semantic analysis are stored in a mutable member of the OpenMPAtomicConstruct node. This follows a precedent of having `typedExpr` member in parser::Expr, for example. This allows the lowering code to avoid duplicated handling of AST nodes. Using a BLOCK construct containing multiple statements for an ATOMIC construct that requires multiple statements is now allowed. In fact, any nesting of such BLOCK constructs is allowed. This implementation will parse, and perform semantic checks for both conditional-update and conditional-update-capture, although no MLIR will be generated for those. Instead, a TODO error will be issues prior to lowering. The allowed forms of the ATOMIC construct were based on the OpenMP 6.0 spec.
5.6 KiB
Flang OpenMP Support
---
local:
---
This document outlines the OpenMP API features supported by Flang. It is intended as a general reference. For the most accurate information on unimplemented features, rely on the compiler’s TODO or “Not Yet Implemented” messages, which are considered authoritative. Flang provides complete implementation of the OpenMP 3.1 specification and partial implementation of OpenMP 4.0, with continued development efforts aimed at extending full support for the latter. The table below outlines the current status of OpenMP 4.0 feature support. Work is ongoing to add support for OpenMP 4.5 and newer versions; a support statement for these will be shared in the future. The table entries are derived from the information provided in the Version Differences subsection of the Features History section in the OpenMP standard.
The feature support information is provided as a table with three columns that are self explanatory. The Status column uses the letters P, Y, N for the implementation status:
- P : Partial. When the implementation is incomplete for a few cases
- Y : Yes. When the implementation is complete
- N : No. When the implementation is absent
Note : No distinction is made between the support in Parser/Semantics, MLIR, Lowering or the OpenMPIRBuilder.
OpenMP 4.0
| Feature | Status | Comments |
|---|---|---|
| proc_bind clause | Y | |
| simd construct | P | linear clause is not supported |
| declare simd construct | N | |
| do simd construct | P | linear clause is not supported |
| target data construct | P | device clause not supported |
| target construct | P | device clause not supported |
| target update construct | P | device clause not supported |
| declare target directive | P | |
| teams construct | P | reduction clause not supported |
| distribute construct | P | dist_schedule clause not supported |
| distribute simd construct | P | dist_schedule and linear clauses are not supported |
| distribute parallel loop construct | P | dist_schedule clause not supported |
| distribute parallel loop simd construct | P | dist_schedule and linear clauses are not supported |
| depend clause | Y | |
| declare reduction construct | N | |
| atomic construct extensions | Y | |
| cancel construct | Y | |
| cancellation point construct | Y | |
| parallel do simd construct | P | linear clause is not supported |
| target teams construct | P | device and reduction clauses are not supported |
| teams distribute construct | P | reduction and dist_schedule clauses not supported |
| teams distribute simd construct | P | reduction, dist_schedule and linear clauses are not supported |
| target teams distribute construct | P | device, reduction and dist_schedule clauses are not supported |
| teams distribute parallel loop construct | P | reduction and dist_schedule clauses are not supported |
| target teams distribute parallel loop construct | P | device, reduction and dist_schedule clauses are not supported |
| teams distribute parallel loop simd construct | P | reduction, dist_schedule, and linear clauses are not supported |
| target teams distribute parallel loop simd construct | P | device, reduction, dist_schedule and linear clauses are not supported |
Extensions
ATOMIC construct
The implementation of the ATOMIC construct follows OpenMP 6.0 with the following extensions:
x = xis an allowed form of ATOMIC UPDATE. This is motivated by the fact that the equivalent formsx = x+0orx = x*1are allowed.- Explicit type conversions are allowed in ATOMIC READ, WRITE or UPDATE constructs, and in the capture statement in ATOMIC UPDATE CAPTURE. The OpenMP spec requires intrinsic- or pointer-assignments, which include (as per the Fortran standard) implicit type conversions. Since such conversions need to be handled, allowing explicit conversions comes at no extra cost.
- A literal
.true.or.false.is an allowed condition in ATOMIC UPDATE COMPARE. [1] - A logical variable is an allowed form of the condition even if its value is not computed within the ATOMIC UPDATE COMPARE construct [1].
expr equalop xis an allowed condition in ATOMIC UPDATE COMPARE. [1]
[1] Code generation for ATOMIC UPDATE COMPARE is not implemented yet.