Lines Matching +full:- +full:- +full:release

3 ! RUN: %python %S/../test_errors.py %s %flang_fc1 %openmp_flags -fopenmp-version=50
8   integer :: i, j = 10, k=-100, a
14 ! At most one memory-order-clause may appear on the construct.
74   !ERROR: At most one RELEASE clause can appear on the UPDATE directive
75   !$omp atomic release release update
79   !ERROR: At most one RELEASE clause can appear on the UPDATE directive
80   !$omp atomic update release release
84   !ERROR: At most one RELEASE clause can appear on the UPDATE directive
85   !$omp atomic release update release
127   !ERROR: At most one RELEASE clause can appear on the CAPTURE directive
128   !$omp atomic release release capture
134   !ERROR: At most one RELEASE clause can appear on the CAPTURE directive
135   !$omp atomic capture release release
141   !ERROR: At most one RELEASE clause can appear on the CAPTURE directive
142   !$omp atomic release capture release
226   !ERROR: At most one RELEASE clause can appear on the WRITE directive
227   !$omp atomic release release write
230   !ERROR: At most one RELEASE clause can appear on the WRITE directive
231   !$omp atomic write release release
234   !ERROR: At most one RELEASE clause can appear on the WRITE directive
235   !$omp atomic release write release
250 !No atomic-clause
262   !ERROR: At most one RELEASE clause can appear on the ATOMIC directive
263   !$omp atomic release release
338 ! If atomic-clause is read then memory-order-clause must not be acq_rel or release.
347   !ERROR: Clause RELEASE is not allowed if clause READ appears on the ATOMIC directive
348   !$omp atomic release read
350   !ERROR: Clause RELEASE is not allowed if clause READ appears on the ATOMIC directive
351   !$omp atomic read release
355 ! If atomic-clause is write then memory-order-clause must not be acq_rel or acquire.
373 ! If atomic-clause is update or not present then memory-order-clause must not be acq_rel or acquire.