[llvm] [delinearize] use update_analyze_test_checks.py in delinearization testcases (PR #153831)
Ryotaro Kasuga via llvm-commits
llvm-commits at lists.llvm.org
Fri Aug 15 13:28:41 PDT 2025
================
@@ -744,7 +744,8 @@ namespace {
void printDelinearization(raw_ostream &O, Function *F, LoopInfo *LI,
ScalarEvolution *SE) {
- O << "Delinearization on function " << F->getName() << ":\n";
+ O << "Printing analysis 'Delinearization' for function '" << F->getName()
+ << "':";
for (Instruction &Inst : instructions(F)) {
// Only analyze loads and stores.
if (!isa<StoreInst>(&Inst) && !isa<LoadInst>(&Inst) &&
----------------
kasuga-fj wrote:
+1 on this.
I also think we should stop checking all loops. Basically, we are only interested in the innermost loop in which the target instruction resides. https://github.com/llvm/llvm-project/blob/495b0ab03f1a2e72adb17d0ee68aaf7d918f734c/llvm/lib/Analysis/Delinearization.cpp#L749-L759
https://github.com/llvm/llvm-project/pull/153831
More information about the llvm-commits
mailing list