aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectScript.cpp
diff options
context:
space:
mode:
authoragozillon <Andrew.Gozillon@amd.com>2024-02-05 18:45:07 +0100
committerGitHub <noreply@github.com>2024-02-05 18:45:07 +0100
commit95fe47ca7e99d999108705640e49075f4c5f39a7 (patch)
tree058295dd368153cb863694a5414ec930274ce1b0 /lldb/source/Commands/CommandObjectScript.cpp
parentea9276d47efb22e26483bd5ad31c2e249ed9846f (diff)
downloadllvm-95fe47ca7e99d999108705640e49075f4c5f39a7.zip
llvm-95fe47ca7e99d999108705640e49075f4c5f39a7.tar.gz
llvm-95fe47ca7e99d999108705640e49075f4c5f39a7.tar.bz2
[Flang][OpenMP] Initial mapping of Fortran pointers and allocatables for target devices (#71766)
This patch seeks to add an initial lowering for pointers and allocatable variables captured by implicit and explicit map in Flang OpenMP for Target operations that take map clauses e.g. Target, Target Update. Target Exit/Enter etc. Currently this is done by treating the type that lowers to a descriptor (allocatable/pointer/assumed shape) as a map of a record type (e.g. a structure) as that's effectively what descriptor types lower to in LLVM-IR and what they're represented as in the Fortran runtime (written in C/C++). The descriptor effectively lowers to a structure containing scalar and array elements that represent various aspects of the underlying data being mapped (lower bound, upper bound, extent being the main ones of interest in most cases) and a pointer to the allocated data. In this current iteration of the mapping we map the structure in it's entirety and then attach the underlying data pointer and map the data to the device, this allows most of the required data to be resident on the device for use. Currently we do not support the addendum (another block of pointer data), but it shouldn't be too difficult to extend this to support it. The MapInfoOp generation for descriptor types is primarily handled in an optimization pass, where it expands BoxType (descriptor types) map captures into two maps, one for the structure (scalar elements) and the other for the pointer data (base address) and links them in a Parent <-> Child relationship. The later lowering processes will then treat them as a conjoined structure with a pointer member map.
Diffstat (limited to 'lldb/source/Commands/CommandObjectScript.cpp')
0 files changed, 0 insertions, 0 deletions