aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp
diff options
context:
space:
mode:
authorFlorian Hahn <flo@fhahn.com>2021-11-27 13:04:28 +0000
committerFlorian Hahn <flo@fhahn.com>2021-11-27 13:04:28 +0000
commit25dad1064bf14b9a24c6e33ef4a9e7f8e951c1e3 (patch)
tree7765d556f2a0771d1160a77dd86d4fa20fe516c9 /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp
parent9f374a74c2aabed998a731ac9f14bd8baa4208ba (diff)
downloadllvm-25dad1064bf14b9a24c6e33ef4a9e7f8e951c1e3.zip
llvm-25dad1064bf14b9a24c6e33ef4a9e7f8e951c1e3.tar.gz
llvm-25dad1064bf14b9a24c6e33ef4a9e7f8e951c1e3.tar.bz2
[DSE] Optimize defining access of defs while walking upwards.
This patch extends the code that walks memory defs upwards to find clobbering accesses to also try to optimize the clobbering defining access. We should be able to find set the optimized access of our starting def (KillingDef), if the following holds: 1. It is the first call of getDomMemoryDef for KillingDef (so Current == KillingDef->getDefiningAccess(). 2. No potentially aliasing defs are skipped. Then if a (partly) aliasing def is encountered, it can be used as optimized access for KillingDef. No further optimizations can be applied to KillingDef. I'd appreciate a careful look, as the existing documentation is not too clear on what is expected for optimized accesses. The motivation for this patch is to use the optimized accesses to cover more cases of redundant stores as follow-up to D111727. Reviewed By: nikic Differential Revision: https://reviews.llvm.org/D112313
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp')
0 files changed, 0 insertions, 0 deletions