aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/MachOObjectFile.cpp
diff options
context:
space:
mode:
authorSlava Zakharin <szakharin@nvidia.com>2024-05-08 16:48:14 -0700
committerGitHub <noreply@github.com>2024-05-08 16:48:14 -0700
commit1710c8cf0f8def4984893e9dd646579de5528d95 (patch)
tree56e7fee99b2c19c9b3e581ddab55d0773a1e2718 /llvm/lib/Object/MachOObjectFile.cpp
parent36d8b37dfaa95b8b4e21cb8269fefb62e1f59c2f (diff)
downloadllvm-1710c8cf0f8def4984893e9dd646579de5528d95.zip
llvm-1710c8cf0f8def4984893e9dd646579de5528d95.tar.gz
llvm-1710c8cf0f8def4984893e9dd646579de5528d95.tar.bz2
[flang] Lowering changes for assigning dummy_scope to hlfir.declare. (#90989)
The lowering produces fir.dummy_scope operation if the current function has dummy arguments. Each hlfir.declare generated for a dummy argument is then using the result of fir.dummy_scope as its dummy_scope operand. This is only done for HLFIR. I was not able to find a reliable way to identify dummy symbols in `genDeclareSymbol`, so I added a set of registered dummy symbols that is alive during the variables instantiation for the current function. The set is initialized during the mapping of the dummy argument symbols to their MLIR values. It is reset right after all variables are instantiated - this is done to avoid generating hlfir.declare operations with dummy_scope for the clones of the dummy symbols (e.g. this happens with OpenMP privatization). If this can be done in a cleaner way, please advise.
Diffstat (limited to 'llvm/lib/Object/MachOObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions