[all-commits] [llvm/llvm-project] adeff9: [flang][OpenMP] Allow utility constructs in specif...

[Krzysztof Parzyszek via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: adeff9f63a24f60b0bf240bf13e40bbf7c1dd0e8
      https://github.com/llvm/llvm-project/commit/adeff9f63a24f60b0bf240bf13e40bbf7c1dd0e8
  Author: Krzysztof Parzyszek <Krzysztof.Parzyszek at amd.com>
  Date:   2025-01-03 (Fri, 03 Jan 2025)

  Changed paths:
    M flang/examples/FlangOmpReport/FlangOmpReportVisitor.cpp
    M flang/include/flang/Parser/parse-tree.h
    M flang/lib/Lower/OpenMP/OpenMP.cpp
    M flang/lib/Parser/openmp-parsers.cpp
    M flang/lib/Parser/unparse.cpp
    M flang/lib/Semantics/canonicalize-omp.cpp
    M flang/lib/Semantics/check-omp-structure.cpp
    M flang/lib/Semantics/check-omp-structure.h
    M flang/test/Parser/OpenMP/error-unparse.f90
    M flang/test/Parser/OpenMP/nothing.f90
    A flang/test/Semantics/OpenMP/error.f90

  Log Message:
  -----------
  [flang][OpenMP] Allow utility constructs in specification part (#121509)

Allow utility constructs (error and nothing) to appear in the
specification part as well as the execution part. The exception is
"ERROR AT(EXECUTION)" which should only be in the execution part.
In case of ambiguity (the boundary between the specification and the
execution part), utility constructs will be parsed as belonging to the
specification part. In such cases move them to the execution part in the
OpenMP canonicalization code.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications