I've added a test for a loop containing a conditional uniform load for
a target that supports masked loads. The test just ensures that we
correctly use gather instructions and have the correct mask.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Seems reasonable to me. Might have liked to see a pseudo-C implementation in the comment above to shorten the first-pass brain parse of the test's intent, but it was not too bad without (and it follows fairly obviously from the title).
| llvm/test/Transforms/LoopVectorize/AArch64/tail-fold-uniform-memops.ll | ||
|---|---|---|
| 2 | you are not checking any debug output, right? So there should be no need for 2>&1. | |
| llvm/test/Transforms/LoopVectorize/AArch64/tail-fold-uniform-memops.ll | ||
|---|---|---|
| 2 | Sure. Shouldn’t this patch also include @ uniform_load so the diff in the follow up patch only shows the changes? | |
you are not checking any debug output, right? So there should be no need for 2>&1.