[llvm] [LoopVectorizer] Rename variable (NFC). (PR #180585)
Jonas Paulsson via llvm-commits
llvm-commits at lists.llvm.org
Mon Feb 9 10:51:30 PST 2026
https://github.com/JonPsson1 created https://github.com/llvm/llvm-project/pull/180585
Since TargetTransformInfo::enableAggressiveInterleaving(bool HasReductions) takes the HasReductions argument, the LoopVectorizer should save its returned value in a variable called AggressivelyInterleave instead of AggressivelyInterleaveReductions.
@fhahn @Mel-Chen
>From a0e3dde923268778e6035b1e4b1ad84f5ec5abee Mon Sep 17 00:00:00 2001
From: Jonas Paulsson <paulsson at linux.vnet.ibm.com>
Date: Mon, 9 Feb 2026 19:44:41 +0100
Subject: [PATCH] Rename variable (NFC)
---
llvm/lib/Transforms/Vectorize/LoopVectorize.cpp | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp b/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
index 68e61c01c65d9..61415f1d5a738 100644
--- a/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
+++ b/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp
@@ -4850,7 +4850,7 @@ LoopVectorizationPlanner::selectInterleaveCount(VPlan &Plan, ElementCount VF,
LLVM_DEBUG(dbgs() << "LV: Loop cost is " << LoopCost << '\n'
<< "LV: IC is " << IC << '\n'
<< "LV: VF is " << VF << '\n');
- const bool AggressivelyInterleaveReductions =
+ const bool AggressivelyInterleave =
TTI.enableAggressiveInterleaving(HasReductions);
if (!ScalarInterleavingRequiresRuntimePointerCheck &&
!ScalarInterleavingRequiresPredication && LoopCost < SmallLoopCost) {
@@ -4951,7 +4951,7 @@ LoopVectorizationPlanner::selectInterleaveCount(VPlan &Plan, ElementCount VF,
// If there are scalar reductions and TTI has enabled aggressive
// interleaving for reductions, we will interleave to expose ILP.
- if (VF.isScalar() && AggressivelyInterleaveReductions) {
+ if (VF.isScalar() && AggressivelyInterleave) {
LLVM_DEBUG(dbgs() << "LV: Interleaving to expose ILP.\n");
// Interleave no less than SmallIC but not as aggressive as the normal IC
// to satisfy the rare situation when resources are too limited.
@@ -4964,7 +4964,7 @@ LoopVectorizationPlanner::selectInterleaveCount(VPlan &Plan, ElementCount VF,
// Interleave if this is a large loop (small loops are already dealt with by
// this point) that could benefit from interleaving.
- if (AggressivelyInterleaveReductions) {
+ if (AggressivelyInterleave) {
LLVM_DEBUG(dbgs() << "LV: Interleaving to expose ILP.\n");
return IC;
}
More information about the llvm-commits
mailing list