I'm renaming the flag because a future patch will add a new
enableOrderedReductions() TTI interface and so the meaning of this
flag will change to be one of forcing the target to enable/disable
them. Also, since other places in LoopVectorize.cpp use the word
'Ordered' instead of 'strict' I changed the flag to match.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Makes sense to me, this also aligns the naming of the other force flags that override the target's cost-model.
llvm/lib/Transforms/Vectorize/LoopVectorize.cpp | ||
---|---|---|
337 | nit: Force the vectorization of loops with in-order (strict) FP reductions. |
nit: Force the vectorization of loops with in-order (strict) FP reductions.
(also: vectorization in American spelling)