diff options
author | Florian Hahn <flo@fhahn.com> | 2022-03-28 16:20:02 +0100 |
---|---|---|
committer | Florian Hahn <flo@fhahn.com> | 2022-03-28 16:20:02 +0100 |
commit | e7bf2ea93472bfdab8c5a31b81f94727f1def07b (patch) | |
tree | c9dc97435b6970a64d1732c93f169fdac24b00b0 /llvm/lib/IR/Module.cpp | |
parent | a7865228b30dc019c0d13d0c81247d90fcad325b (diff) | |
download | llvm-e7bf2ea93472bfdab8c5a31b81f94727f1def07b.zip llvm-e7bf2ea93472bfdab8c5a31b81f94727f1def07b.tar.gz llvm-e7bf2ea93472bfdab8c5a31b81f94727f1def07b.tar.bz2 |
[LV] Move code to place induction increment to VPlan post-processing.
This patch moves the code to set the correct incoming block for the
backedge value to VPlan::execute.
When generating the phi node, the backedge value is temporarily added
using the pre-header as incoming block. The invalid phi node will be
fixed up during VPlan::execute after main VPlan code generation.
At the same time, the backedge value is also moved to the latch.
This change removes the requirement to create the latch block up-front
for VPWidenIntOrFpInductionRecipe::execute, which in turn will enable
modeling the pre-header in VPlan.
As an alternative, the increment could be modeled as separate recipe,
but that would require more work and a bit of redundant code, as we need
to create the step-vector during VPWidenIntOrFpInductionRecipe::execute
anyways, to create the values for different parts.
Reviewed By: Ayal
Differential Revision: https://reviews.llvm.org/D121617
Diffstat (limited to 'llvm/lib/IR/Module.cpp')
0 files changed, 0 insertions, 0 deletions