aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/AssignmentTrackingAnalysis.cpp
diff options
context:
space:
mode:
authorjeanPerier <jperier@nvidia.com>2024-09-19 13:52:58 +0200
committerGitHub <noreply@github.com>2024-09-19 13:52:58 +0200
commit94c024adedcb53059c29d7c2d62982053b60e86a (patch)
tree219f2907f2dd1f94738a3b728a3e5f05c9d9d429 /llvm/lib/CodeGen/AssignmentTrackingAnalysis.cpp
parent96ac627238dc515efdd61e5ddeda78cd17014fa5 (diff)
downloadllvm-94c024adedcb53059c29d7c2d62982053b60e86a.zip
llvm-94c024adedcb53059c29d7c2d62982053b60e86a.tar.gz
llvm-94c024adedcb53059c29d7c2d62982053b60e86a.tar.bz2
[flang][lowering] delay stack save/restor emission in elemental calls (#109142)
stack save/restore emitted for character elemental function result allocation inside hlfir.elemental in lowering created memory bugs because result memory is actually still used after the stack restore when lowering the elemental into a loop where the result element is copied into the array result storage. Instead of adding special handling for stack save/restore in lowering, just avoid emitting those since the stack reclaim pass is able to emit them in the generated loop. Not having those stack save/restore will also help optimizations that want to elide the temporary allocation for the element result when that is possible.
Diffstat (limited to 'llvm/lib/CodeGen/AssignmentTrackingAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions