The changeset contains a test that highlights the problem with forced vectorization and when number of required runtime checks exceeds some limit.
In the case of vec_foced it can be see that no overlap runtime checks were generated, which results to invalid vector code.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
This comment was removed by nikolaypanchenko.
Comment Actions
LGTM, thanks! I still think it would be slightly preferable to not rely on debug output in the test and run it unconditionally, but don't have strong feelings about it.
llvm/test/Transforms/LoopVectorize/memcheck_threashold_vec_forced.ll | ||
---|---|---|
53 | nit: IMO it would be slightly more readable to put this at the end of the function and rename it to exit. (same below) | |
109 | Looks like the custom check lines cause this warning by the script. Perhaps remove the lines? |
nit: IMO it would be slightly more readable to put this at the end of the function and rename it to exit. (same below)