summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2019-02-05 22:58:45 +0000
committerSanjay Patel <spatel@rotateright.com>2019-02-05 22:58:45 +0000
commitcddb1e54697d0eed7329f4bee8878802b388ab29 (patch)
treed3f16fedd30c8ccf6cccf18b5f099d84f78e120a /lldb/packages/Python/lldbsuite/test/expression_command
parent1b8df427121e3d7edf5cfaf0f3e3550ed2091d62 (diff)
downloadbcm5719-llvm-cddb1e54697d0eed7329f4bee8878802b388ab29.tar.gz
bcm5719-llvm-cddb1e54697d0eed7329f4bee8878802b388ab29.zip
[InstCombine] limit extracting shuffle transform based on uses
As discussed in D53037, this can lead to worse codegen, and we don't generally expect the backend to be able to optimize arbitrary shuffles. If there's only one use of the 1st shuffle, that means it's getting removed, so that should always be safe. llvm-svn: 353235
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud