summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2019-04-03 23:28:30 +0000
committerCraig Topper <craig.topper@intel.com>2019-04-03 23:28:30 +0000
commit52cac4b79f97b1793ad06e503a5a62a24e06859c (patch)
tree4ba1913eaa4322cf1bc5097dd0cc4e9daeeca50d /lldb/packages/Python/lldbsuite/test/python_api
parent477008bd5034a54cb7bddd0e635c19fdffaa524c (diff)
downloadbcm5719-llvm-52cac4b79f97b1793ad06e503a5a62a24e06859c.tar.gz
bcm5719-llvm-52cac4b79f97b1793ad06e503a5a62a24e06859c.zip
[X86] Remove CustomInserter pseudos for MONITOR/MONITORX/CLZERO. Use custom instruction selection instead.
This custom inserter existed so we could do a weird thing where we pretended that the instructions support a full address mode instead of taking a pointer in EAX/RAX. I think was largely so we could be pointer size agnostic in the isel pattern. To make this work we would then put the address into an LEA into EAX/RAX in front of the instruction after isel. But the LEA is overkill when we just have a base pointer. So we end up using the LEA as a slower MOV instruction. With this change we now just do custom selection during isel instead and just assign the incoming address of the intrinsic into EAX/RAX based on its size. After the intrinsic is selected, we can let isel take care of selecting an LEA or other operation to do any address computation needed in this basic block. I've also split the instruction into a 32-bit mode version and a 64-bit mode version so the implicit use is properly sized based on the pointer. Without this we get comments in the assembly output about killing eax and defing rax or vice versa depending on whether we define the instruction to use EAX/RAX. llvm-svn: 357652
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud