[llvm] [LV] Teach LoopVectorizationLegality about struct vector calls (PR #119221)
Florian Hahn via llvm-commits
llvm-commits at lists.llvm.org
Wed Dec 18 11:25:07 PST 2024
================
@@ -943,11 +955,24 @@ bool LoopVectorizationLegality::canVectorizeInstrs() {
if (CI && !VFDatabase::getMappings(*CI).empty())
VecCallVariantsFound = true;
+ auto canWidenInstruction = [this](Instruction const &Inst) {
+ Type *InstTy = Inst.getType();
+ if (isa<CallInst>(Inst) && isa<StructType>(InstTy) &&
+ canWidenCallReturnType(InstTy)) {
+ StructVecCallFound = true;
----------------
fhahn wrote:
Do we need this extra global state? Can we instead emit the new message for calls here when we encounter them, similar to other return types we cannot handle?
https://github.com/llvm/llvm-project/pull/119221
More information about the llvm-commits
mailing list