summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/overloaded-functions/TestOverloadedFunctions.py
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2019-04-24 18:02:07 +0000
committerCraig Topper <craig.topper@intel.com>2019-04-24 18:02:07 +0000
commit882ca6d48483938bd1f3b42c279f9aa8364149a7 (patch)
treeb44a21e7a28a2e10751610393824f1af161743e8 /lldb/packages/Python/lldbsuite/test/lang/cpp/overloaded-functions/TestOverloadedFunctions.py
parent25c6a5073dfc9573bf14dcc0ed1d0f1950175eba (diff)
downloadbcm5719-llvm-882ca6d48483938bd1f3b42c279f9aa8364149a7.tar.gz
bcm5719-llvm-882ca6d48483938bd1f3b42c279f9aa8364149a7.zip
[X86] Remove dead nodes left after ReplaceAllUsesWith calls during address matching
ReplaceAllUsesWith doesn't remove the node that was replaced. So its left around in the graph messing up use counts on other nodes. One thing to note, is that this isn't valid if the node being deleted is the root node of an LEA match that gets rejected. In that case the node needs to stay alive because the isel table walking code would still have a reference to it that its going to try to match next. I don't think that's the case here though because the nodes being deleted here should be "and", "srl", and "zero_extend" none of which can be the root node of an LEA match. Differential Revision: https://reviews.llvm.org/D61048 llvm-svn: 359121
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/overloaded-functions/TestOverloadedFunctions.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud