6533ad04ed
The structure is - OmpBeginDirective (aka OmpDirectiveSpecification) - Block - optional<OmpEndDirective> (aka optional<OmpDirectiveSpecification>) The OmpBeginDirective and OmpEndDirective are effectively different names for OmpDirectiveSpecification. They exist to allow the semantic analyses to distinguish between the beginning and the ending of a block construct without maintaining additional context. The actual changes are in the parser: parse-tree.h and openmp-parser.cpp in particular. The rest is simply changing the way the directive/clause information is accessed (typically for the simpler). All standalone and block constructs now use OmpDirectiveSpecification to store the directive/clause information.
18 lines
736 B
Fortran
18 lines
736 B
Fortran
! REQUIRES: openmp_runtime
|
|
! RUN: %flang_fc1 %openmp_flags -fdebug-dump-parse-tree -fopenmp -fopenmp-version=50 %s | FileCheck --ignore-case %s
|
|
! RUN: %flang_fc1 %openmp_flags -fdebug-unparse -fopenmp -fopenmp-version=50 %s | FileCheck --ignore-case --check-prefix="CHECK-UNPARSE" %s
|
|
|
|
!CHECK: OmpDirectiveName -> llvm::omp::Directive = task
|
|
!CHECK: OmpClauseList -> OmpClause -> Detach -> OmpDetachClause -> OmpObject -> Designator -> DataRef -> Name = 'event'
|
|
|
|
!CHECK-UNPARSE: INTEGER(KIND=8_4) event
|
|
!CHECK-UNPARSE: !$OMP TASK DETACH(event)
|
|
!CHECK-UNPARSE: !$OMP END TASK
|
|
subroutine task_detach
|
|
use omp_lib
|
|
implicit none
|
|
integer(kind=omp_event_handle_kind) :: event
|
|
!$omp task detach(event)
|
|
!$omp end task
|
|
end subroutine
|