This patch updates VPWidenIntOrFpInductionRecipe to hold the start value
for the induction variable. This makes the start value explicit and
allows for adjusting the start value for a VPlan.
The flexibility will be used in further patches.
Paths
| Differential D92129
[VPlan] Keep start value in VPWidenIntOrFpInductionRecipe (NFC). ClosedPublic Authored by fhahn on Nov 25 2020, 1:12 PM.
Details Summary This patch updates VPWidenIntOrFpInductionRecipe to hold the start value The flexibility will be used in further patches.
Diff Detail
Event TimelineComment Actions Good step towards representing more Values, and in particular recording InductionDescriptor information, in VPlan!
This revision is now accepted and ready to land.Jan 5 2021, 2:20 PM This revision was landed with ongoing or failed builds.Jan 6 2021, 3:47 AM Closed by commit rG816dba48af49: [VPlan] Keep start value in VPWidenIntOrFpInductionRecipe (NFC). (authored by fhahn). · Explain Why This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 313679 llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
llvm/lib/Transforms/Vectorize/VPRecipeBuilder.h
llvm/lib/Transforms/Vectorize/VPlan.h
llvm/lib/Transforms/Vectorize/VPlanTransforms.cpp
|
getStateValue() can be asserted to be a live-in, i.e., have a null Def, and then we can obtain its underlying Value (the latter possibly asserted to be non null)?