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.
82 lines
1.5 KiB
Fortran
82 lines
1.5 KiB
Fortran
!RUN: %python %S/../test_errors.py %s %flang -fopenmp -fopenmp-version=60
|
|
|
|
subroutine f00
|
|
integer :: x, v
|
|
! The end-directive is optional in ATOMIC WRITE. Expect no diagnostics.
|
|
!$omp atomic write
|
|
x = v + 1
|
|
|
|
!$omp atomic write
|
|
x = v + 3
|
|
!$omp end atomic
|
|
end
|
|
|
|
subroutine f01
|
|
integer, pointer :: x, v
|
|
! Intrinsic assignment and pointer assignment are both ok. Expect no
|
|
! diagnostics.
|
|
!$omp atomic write
|
|
x = 2 * v + 3
|
|
|
|
!$omp atomic write
|
|
x => v
|
|
end
|
|
|
|
subroutine f02(i)
|
|
integer :: i, v
|
|
interface
|
|
function p(i)
|
|
integer, pointer :: p
|
|
integer :: i
|
|
end
|
|
end interface
|
|
|
|
! Atomic variable can be a function reference. Expect no diagostics.
|
|
!$omp atomic write
|
|
p(i) = v
|
|
end
|
|
|
|
subroutine f03
|
|
integer :: x(3), y(5), v(3)
|
|
|
|
!$omp atomic write
|
|
!ERROR: Atomic variable x should be a scalar
|
|
x = v
|
|
|
|
!$omp atomic write
|
|
!ERROR: Atomic variable y(2_8:4_8:1_8) should be a scalar
|
|
y(2:4) = v
|
|
end
|
|
|
|
subroutine f04
|
|
integer :: x, y(3), v
|
|
|
|
!$omp atomic write
|
|
!ERROR: Within atomic operation x and x+1_4 access the same storage
|
|
x = x + 1
|
|
|
|
! Accessing same array, but not the same storage. Expect no diagnostics.
|
|
!$omp atomic write
|
|
y(1) = y(2)
|
|
end
|
|
|
|
subroutine f06
|
|
character :: x, v
|
|
|
|
!$omp atomic write
|
|
!ERROR: Atomic variable x cannot have CHARACTER type
|
|
x = v
|
|
end
|
|
|
|
subroutine f07
|
|
integer, allocatable :: x
|
|
integer :: v
|
|
|
|
allocate(x)
|
|
|
|
!$omp atomic write
|
|
!ERROR: Atomic variable x cannot be ALLOCATABLE
|
|
x = v
|
|
end
|
|
|