The legacy LoopVectorize has a dependency on InjectTLIMappingsLegacy.
That cannot be expressed in the new PM since they are both normal
passes. Explicitly add -inject-tli-mappings as a pass.
Follow-up to https://reviews.llvm.org/D86492.
Paths
| Differential D86561
[test] Add -inject-tli-mapping to -loop-vectorize -vector-library tests ClosedPublic Authored by aeubanks on Aug 25 2020, 11:17 AM.
Details Summary The legacy LoopVectorize has a dependency on InjectTLIMappingsLegacy. Follow-up to https://reviews.llvm.org/D86492.
Diff Detail
Event TimelineComment Actions LGTM
This revision is now accepted and ready to land.Aug 25 2020, 11:48 AM Closed by commit rGdf5576a85208: [test] Add -inject-tli-mapping to -loop-vectorize -vector-library tests (authored by aeubanks). · Explain WhyAug 25 2020, 11:55 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 287722 llvm/test/Transforms/LoopVectorize/PowerPC/massv-altivec.ll
llvm/test/Transforms/LoopVectorize/PowerPC/massv-calls.ll
llvm/test/Transforms/LoopVectorize/PowerPC/massv-nobuiltin.ll
llvm/test/Transforms/LoopVectorize/PowerPC/massv-unsupported.ll
llvm/test/Transforms/LoopVectorize/PowerPC/widened-massv-call.ll
llvm/test/Transforms/LoopVectorize/X86/svml-calls-finite.ll
llvm/test/Transforms/LoopVectorize/X86/svml-calls.ll
llvm/test/Transforms/LoopVectorize/X86/veclib-calls.ll
|
Side note: That looks weird. Running the whole -O2 pipeline followed by an extra round of loop-vectorize?