forked from OSchip/llvm-project
0a515595a7
This is a long-awaited follow-up suggested in D33578. Since then, we've picked up even more opportunities for vector narrowing from changes like D53784, so there are a lot of test diffs. Apart from 2-3 strange cases, these are all wins. I've structured this to be no-functional-change-intended for any target except for x86 because I couldn't tell if AArch64, ARM, and AMDGPU would improve or not. All of those targets have existing regression tests (4, 4, 10 files respectively) that would be affected. Also, Hexagon overrides the shouldReduceLoadWidth() hook, but doesn't show any regression test diffs. The trade-off is deciding if an extra vector load is better than a single wide load + extract_subvector. For x86, this is almost always better (on paper at least) because we often can fold loads into subsequent ops and not increase the official instruction count. There's also some unknown -- but potentially large -- benefit from using narrower vector ops if wide ops are implemented with multiple uops and/or frequency throttling is avoided. Differential Revision: https://reviews.llvm.org/D54073 llvm-svn: 346595 |
||
|---|---|---|
| .. | ||
| broadcast-scalar-fp.ll | ||
| broadcast-scalar-int.ll | ||
| broadcast-vector-fp.ll | ||
| broadcast-vector-int.ll | ||
| duplicate-high.ll | ||
| duplicate-low.ll | ||
| in_lane_permute.ll | ||
| partial_permute.ll | ||
| permute.ll | ||
| shuffle-interleave.ll | ||
| shuffle-vec.ll | ||
| shuffle.ll | ||
| unpack.ll | ||