summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/frame
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2017-05-27 14:07:03 +0000
committerSanjay Patel <spatel@rotateright.com>2017-05-27 14:07:03 +0000
commit33f4a9728741b1305496ec89f5b472a57e21a32b (patch)
tree647340b9f5eb29c43204f874206ff6a7cae58647 /lldb/packages/Python/lldbsuite/test/python_api/frame
parent7aa22859b66223c59a5dacc45e8bd7535659057b (diff)
downloadbcm5719-llvm-33f4a9728741b1305496ec89f5b472a57e21a32b.tar.gz
bcm5719-llvm-33f4a9728741b1305496ec89f5b472a57e21a32b.zip
[DAGCombiner] use narrow load to avoid vector extract
If we have (extract_subvector(load wide vector)) with no other users, that can just be (load narrow vector). This is intentionally conservative. Follow-ups may loosen the one-use constraint to account for the extract cost or just remove the one-use check. The memop chain updating is based on code that already exists multiple times in x86 lowering, so that should be pulled into a helper function as a follow-up. Background: this is a potential improvement noticed via regressions caused by making x86's peekThroughBitcasts() not loop on consecutive bitcasts (see comments in D33137). Differential Revision: https://reviews.llvm.org/D33578 llvm-svn: 304072
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/frame')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud