[PATCH] D36220: [Loop Vectorize] Added a separate metadata
Hal Finkel via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Tue Aug 22 14:17:08 PDT 2017
hfinkel added a comment.
In https://reviews.llvm.org/D36220#848365, @KennethH wrote:
> I have a question:
>
> Is there any reason not to mark the scalar loop and the vectorized version with the "llvm.loop.vectorize.width" and "llvm.loop.interleave.count" metadata reflecting the real outcome from the LV.
> I.e 1, 1 for the scalar loop and VF, UF for the vectorized version? That would be possible after this change.
>
> Our out of tree compiler have later loop passes that could benefit from that information. I do not know if would be of any use for any of the in-tree targets or if it would hurt something.
I'm not clear on how a later pass might use that information in a robust way. Can you please elaborate?
Repository:
rL LLVM
https://reviews.llvm.org/D36220
More information about the llvm-commits
mailing list