[llvm] [LoopVectorizer][AArch64] Move getMinTripCountTailFoldingThreshold later. (PR #132170)
David Sherwood via llvm-commits
llvm-commits at lists.llvm.org
Wed Mar 26 04:30:49 PDT 2025
================
@@ -1,8 +1,8 @@
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py UTC_ARGS: --version 5
; REQUIRES: asserts
-; RUN: opt -S < %s -p loop-vectorize -debug-only=loop-vectorize -mattr=+sve 2>%t | FileCheck %s --check-prefixes=CHECK,CHECK-VS1
+; RUN: opt -S < %s -p "loop-vectorize,simplifycfg" -debug-only=loop-vectorize -mattr=+sve 2>%t | FileCheck %s --check-prefixes=CHECK,CHECK-VS1
----------------
david-arm wrote:
Thanks, I know that @fhahn has a PR in progress for removing loop regions. In my opinion, one of the benefits of testing purely the loop vectoriser output here is that when such vplan changes happen it should be more obvious what effect that has on these tests. But perhaps this is just personal preference!
https://github.com/llvm/llvm-project/pull/132170
More information about the llvm-commits
mailing list