summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support/FileOutputBuffer.cpp
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2017-04-30 22:44:51 +0000
committerSanjay Patel <spatel@rotateright.com>2017-04-30 22:44:51 +0000
commitad13826aea229cbafa2093a5069c4c6335299736 (patch)
tree8d2f5db6494d7e65a80422ab6474bc9597afb468 /llvm/lib/Support/FileOutputBuffer.cpp
parent57fa1de516ac1ebb1bef112786bb0c0a18c90ea4 (diff)
downloadbcm5719-llvm-ad13826aea229cbafa2093a5069c4c6335299736.tar.gz
bcm5719-llvm-ad13826aea229cbafa2093a5069c4c6335299736.zip
[DAGCombiner] shrink/widen a vselect to match its condition operand size (PR14657)
We discussed shrinking/widening of selects in IR in D26556, and I'll try to get back to that patch eventually. But I'm hoping that this transform is less iffy in the DAG where we can check legality of the select that we want to produce. A few things to note: 1. We can't wait until after legalization and do this generically because (at least in the x86 tests from PR14657), we'll have PACKSS and bitcasts in the pattern. 2. This might benefit more of the SSE codegen if we lifted the legal-or-custom requirement, but that requires a closer look to make sure we don't end up worse. 3. There's a 'vblendv' opportunity that we're missing that results in andn/and/or in some cases. That should be fixed next. 4. I'm assuming that AVX1 offers the worst of all worlds wrt uneven ISA support with multiple legal vector sizes, but if there are other targets like that, we should add more tests. 5. There's a codegen miracle in the multi-BB tests from PR14657 (the gcc auto-vectorization tests): despite IR that is terrible for the target, this patch allows us to generate the optimal loop code because something post-ISEL is hoisting the splat extends above the vector loops. Differential Revision: https://reviews.llvm.org/D32620 llvm-svn: 301781
Diffstat (limited to 'llvm/lib/Support/FileOutputBuffer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud