summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py
diff options
context:
space:
mode:
authorPhilip Reames <listmail@philipreames.com>2019-03-12 19:12:33 +0000
committerPhilip Reames <listmail@philipreames.com>2019-03-12 19:12:33 +0000
commit18408d5e7986fcda4d7ac2e3533a07f7c43a5d72 (patch)
treee5579131a7737c4c7437279c1d04782932d4a4a8 /lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py
parent9cc10fc926526139559a88d1ac2b13f563cba7f3 (diff)
downloadbcm5719-llvm-18408d5e7986fcda4d7ac2e3533a07f7c43a5d72.tar.gz
bcm5719-llvm-18408d5e7986fcda4d7ac2e3533a07f7c43a5d72.zip
[CodeGen] Add MMOs to statepoint nodes during SelectionDAG
The existing statepoint lowering code does something odd; it adds machine memory operands post instruction selection. This was copied from the stackmap/patchpoint implementation, but appears to be non-idiomatic. This change is largely NFC. It moves the MMO creation logic into SelectionDAG building. It ends up not quite being NFC because the size of the stack slot is reflected in the MMO. The old code blindly used pointer size for the MMO size, which appears to have always been incorrect for larger values. It just happened nothing actually relied on the MMOs, so it worked out okay. For context, I'm planning on removing the MOVolatile flag from these in a future commit, and then removing the MOStore flag from deopt spill slots in a separate one. Doing so is motivated by a small test case where we should be able to better schedule spill slots, but don't do so due to a memory use/def implied by the statepoint. Differential Revision: https://reviews.llvm.org/D59106 llvm-svn: 355953
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud