diff options
author | Raghu Maddhipatla <7686592+raghavendhra@users.noreply.github.com> | 2024-04-11 10:26:54 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-04-11 10:26:54 -0500 |
commit | 298ea9bfd50ca41c77e45065700df06adb6264ae (patch) | |
tree | 9578053f0ced9d350de0d7bd0c23bd05bba29be1 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp | |
parent | 198ffb85314f7741ed048de67d68ca83bb30e16e (diff) | |
download | llvm-298ea9bfd50ca41c77e45065700df06adb6264ae.zip llvm-298ea9bfd50ca41c77e45065700df06adb6264ae.tar.gz llvm-298ea9bfd50ca41c77e45065700df06adb6264ae.tar.bz2 |
[Flang] [OpenMP] [MLIR] [Lowering] Add lowering support for IS_DEVICE_PTR and HAS_DEVICE_ADDR clauses on OMP TARGET directive. (#88206)
Added lowering support for IS_DEVICE_PTR and HAS_DEVICE_ADDR clauses for
OMP TARGET directive and added related tests for these changes.
IS_DEVICE_PTR and HAS_DEVICE_ADDR clauses apply to OMP TARGET directive
OpenMP spec states
The **is_device_ptr** clause indicates that its list items are device
pointers.
The **has_device_addr** clause indicates that its list items already
have device addresses and therefore they may be directly accessed from a
target device.
Whereas USE_DEVICE_PTR and USE_DEVICE_ADDR clauses apply to OMP TARGET
DATA directive and OpenMP spec for them states
Each list item in the **use_device_ptr** clause results in a new list
item that is a device pointer that refers to a device address
Each list item in a **use_device_addr** clause that is present in the
device data environment is treated as if it is implicitly mapped by a
map clause on the construct with a map-type of alloc
Fixed build error caused by Squash merge which needs rebase
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions