| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Turns out I'd already added exactly the same test under the name non_unit_stride.
llvm-svn: 371777
|
| |
|
|
| |
llvm-svn: 371769
|
| |
|
|
| |
llvm-svn: 371747
|
| |
|
|
|
|
|
|
|
|
| |
Implement a TODO from rL371452, and handle loop invariant addresses in predicated blocks. If we can prove that the load is safe to speculate into the header, then we can avoid using a masked.load in favour of a normal load.
This is mostly about vectorization robustness. In the common case, it's generally expected that LICM/LoadStorePromotion would have eliminated such loads entirely.
Differential Revision: https://reviews.llvm.org/D67372
llvm-svn: 371745
|
| |
|
|
| |
llvm-svn: 371456
|
| |
|
|
| |
llvm-svn: 371455
|
| |
|
|
|
|
|
|
|
|
|
|
| |
If we're vectorizing a load in a predicated block, check to see if the load can be speculated rather than predicated. This allows us to generate a normal vector load instead of a masked.load.
To do so, we must prove that all bytes accessed on any iteration of the original loop are dereferenceable, and that all loads (across all iterations) are properly aligned. This is equivelent to proving that hoisting the load into the loop header in the original scalar loop is safe.
Note: There are a couple of code motion todos in the code. My intention is to wait about a day - to be sure this sticks - and then perform the NFC motion without furthe review.
Differential Revision: https://reviews.llvm.org/D66688
llvm-svn: 371452
|
|
|
llvm-svn: 369959
|
