Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Thanks for following up! Adding some thoughts to consider.
llvm/lib/Transforms/Vectorize/VPlan.h | ||
---|---|---|
1133 | Worth indicating which of these produce a value per iteration, per part, per lane? | |
1135 | Worth adding that this induction controls the vector loop, by comparing it with the vector trip count? | |
1137 | Worth adding that this is done by introducing an independent vector header phi? | |
1139 | So perhaps a more consistent name would be VPScalarIntOrFpInductionRecipe? | |
1141 | So perhaps a more consistent name would be VPPointerInductionRecipe? |
llvm/lib/Transforms/Vectorize/VPlan.h | ||
---|---|---|
1133 | Thanks, updated! | |
1135 | Added, thanks! | |
1139 | Updated the wording, but kept the name for now to just reflect the current realities in the documentation, thanks! | |
1141 | I am planning to handle the non-widening case by using derived IV + scalar steps in future patches. |
Ship it, thanks!
Add [NFC] to title?
Relate to recent IV recipe patches in commit message?
llvm/lib/Transforms/Vectorize/VPlan.h | ||
---|---|---|
1138 | nit: worth emphasizing - "a [single] scalar PHI" | |
1141 | nit: "vector phis for each part" >> "a vector PHI per-part", to be more consistent with above and below? | |
1143 | "Produces a single scalar value per iteration" | |
1147 | "vector phis" - better use either "phi" or "PHI" consistently. Worth adding that vector phis are produced per-part and scalar values per-lane? |
Worth indicating which of these produce a value per iteration, per part, per lane?