[PATCH] D49489: [VPlan] VPlan version of InterleavedAccessInfo.
Florian Hahn via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Tue Nov 13 06:35:56 PST 2018
fhahn added a comment.
In https://reviews.llvm.org/D49489#1296800, @rengolin wrote:
> So, IIUC, the way you only get the interleave info on instructions and map to VPlan is because we don't yet have scalar evolution in VPlan, so we need to do that in Instruction and then map to VPInstruction.
>
> In the future, once we can (perhaps using the same template technique) have SCEV on VPlan, we won't need the Old2New map anymore, and then the analysis will be independent of the underlying type.
>
> Di I get that right?
Exactly, using the underlying plain IR values is used for the initial implementation, until we have something like SCEV for VPlan and can do the whole analysis on top of VPlan.
https://reviews.llvm.org/D49489
More information about the llvm-commits
mailing list