diff options
author | agozillon <Andrew.Gozillon@amd.com> | 2024-05-03 14:10:28 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-05-03 14:10:28 +0200 |
commit | 5850f6ba9b2c14d8457c6e8455483a20b2bf3636 (patch) | |
tree | 046b1dc738dbeb26b4c7fab626cb30ccee45935a /clang/lib/CodeGen/CodeGenFunction.cpp | |
parent | 91446e2aa687ec57ad88dc0df793d0c6e694a7c9 (diff) | |
download | llvm-5850f6ba9b2c14d8457c6e8455483a20b2bf3636.zip llvm-5850f6ba9b2c14d8457c6e8455483a20b2bf3636.tar.gz llvm-5850f6ba9b2c14d8457c6e8455483a20b2bf3636.tar.bz2 |
[Flang][OpenMP] Parse and semantically analyze common blocks in map clauses correctly (#89847)
Currently, you cannot provide the common block syntax that you should be
able to provide for map clauses (and that you can for declare target)
e.g.:
` !$omp target map(tofrom: /var/)`
This PR seeks to change that and allow this syntax via a small tweak,
which may also allow a wider range of types to be provided without issue
as well via the utilisation of ResolveOmpObject a helper function used
by the majority of other OmpObject handling clauses.
A by product of this change, is that we now emit an error for the
following syntax, when provided to map clauses with an assumed size
array:
`!$omp target map(arr(:))`
This seems inline with the specification from what I understand of it
(do feel free to correct me if that is not your reading or I am
incorrect!) and other OpenMP compilers i.e. gfortran, ifx, ifort.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenFunction.cpp')
0 files changed, 0 insertions, 0 deletions