aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen/CodeGenModule.cpp
diff options
context:
space:
mode:
authorRazvan Lupusoru <razvan.lupusoru@gmail.com>2024-12-09 15:14:48 -0800
committerGitHub <noreply@github.com>2024-12-09 15:14:48 -0800
commita0eb794da8b8c1e423e4b3100a137faf3844406f (patch)
tree97063f48735904c26e6b84ed155c7ce798a31e6b /clang/lib/CodeGen/CodeGenModule.cpp
parent0e70289f373d40f3f8a4cc5c35dd02bfe909ca83 (diff)
downloadllvm-a0eb794da8b8c1e423e4b3100a137faf3844406f.zip
llvm-a0eb794da8b8c1e423e4b3100a137faf3844406f.tar.gz
llvm-a0eb794da8b8c1e423e4b3100a137faf3844406f.tar.bz2
[MLIR][acc] Introduce varType to acc data clause operations (#119007)
The acc data clause operations hold an operand named `varPtr`. This was intended to hold a pointer to a variable - where the element type of that pointer specifies the type of the variable. However, for both memref and llvm dialects, this assumption is not true. This is because memref element type for cases like memref<10xf32> is simply f32 and for LLVM, after opaque pointers, the variable type is no longer recoverable. Thus, introduce varType to ensure that appropriate semantics are kept. Both the parser and printer for this new type attribute allow it to not be specified in cases where a dialect's getElementType() applied to `varPtr`'s type has a recoverable type. And more specifically, for FIR, no changes are needed in the MLIR unit tests.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions