[all-commits] [llvm/llvm-project] 5e275e: [NFC][VPlan] Split `makeMemOpWideningDecisions` in...
Andrei Elovikov via All-commits
all-commits at lists.llvm.org
Tue May 5 11:23:57 PDT 2026
Branch: refs/heads/users/eas/mem-widen-subpasses
Home: https://github.com/llvm/llvm-project
Commit: 5e275ef6a33ee20722a2f36cced84fa5630ab1f6
https://github.com/llvm/llvm-project/commit/5e275ef6a33ee20722a2f36cced84fa5630ab1f6
Author: Andrei Elovikov <andrei.elovikov at sifive.com>
Date: 2026-05-05 (Tue, 05 May 2026)
Changed paths:
M llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
M llvm/lib/Transforms/Vectorize/VPlanTransforms.cpp
M llvm/lib/Transforms/Vectorize/VPlanTransforms.h
M llvm/test/Transforms/LoopVectorize/VPlan/vplan-print-after-all.ll
Log Message:
-----------
[NFC][VPlan] Split `makeMemOpWideningDecisions` into subpasses
The idea is to have handling of strided memory operations (either from
https://github.com/llvm/llvm-project/pull/147297 or for VPlan-based
multiversioning for unit-strided accesses) done after some mandatory
processing has been performed (e.g., some types **must** be scalarized)
but before legacy CM's decision to widen (gather/scatter) or scalarize
has been committed.
And in longer term, we can uplift all other memory widening decision to
be done here directly at VPlan level. I expect this structure would also
be beneficial for that.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list