aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-objdump/llvm-objdump.cpp
diff options
context:
space:
mode:
authorTom Eccles <tom.eccles@arm.com>2023-07-07 13:00:11 +0000
committerTom Eccles <tom.eccles@arm.com>2023-07-11 10:32:43 +0000
commita918df1716e28c4122452dc7dfe6b67412bbb900 (patch)
tree91b6a9651a2bcd16122ffe13486469ebf6bbcefc /llvm/tools/llvm-objdump/llvm-objdump.cpp
parent77b3f890ccad711184d2a2a9ddcef351051d4dd5 (diff)
downloadllvm-a918df1716e28c4122452dc7dfe6b67412bbb900.zip
llvm-a918df1716e28c4122452dc7dfe6b67412bbb900.tar.gz
llvm-a918df1716e28c4122452dc7dfe6b67412bbb900.tar.bz2
[flang][hlfir] use adaptor in associate bufferization
The associate operation checks if it is the only use of the hlfir.expr, and if so it can take ownership of the hlfir.expr instead of copying it (move semantics). If this check is done by accessing the associate operation's arguments directly (not through the AssociateOpAdaptor), the expression uses will contain some operations which have been deleted. These can include prior copies of the same associate operation, if that operation was cloned (e.g. to lower a hlfir.elemental into a fir.do_loop). Accessing the bufferized expression instead of the old hlfir.expr through the adaptor avoids this false positive. Differential Revision: https://reviews.llvm.org/D154715
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions