57 lines · plain
1; Test that SCEV gets invalidated when one of its dependencies is invalidated.2;3; Each of the RUNs checks that the pass manager runs SCEV, then invalidates it4; due to a dependency being invalidated, and then re-urns it. This will5; directly fail and indicates a failure that would occur later if we ddidn't6; invalidate SCEV in this way.7 8target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"9target triple = "x86_64-unknown-linux-gnu"10 11; RUN: opt < %s -passes='require<scalar-evolution>,invalidate<domtree>,print<scalar-evolution>' \12; RUN: -debug-pass-manager -disable-output 2>&1 \13; RUN: | FileCheck %s -check-prefixes=CHECK,CHECK-DT-INVALIDATE14;15; CHECK-DT-INVALIDATE: Running pass: RequireAnalysisPass16; CHECK-DT-INVALIDATE: Running analysis: ScalarEvolutionAnalysis17; CHECK-DT-INVALIDATE: Running analysis: DominatorTreeAnalysis18; CHECK-DT-INVALIDATE: Running pass: InvalidateAnalysisPass19; CHECK-DT-INVALIDATE: Invalidating analysis: DominatorTreeAnalysis20; CHECK-DT-INVALIDATE: Running pass: ScalarEvolutionPrinterPass21; CHECK-DT-INVALIDATE: Running analysis: ScalarEvolutionAnalysis22; CHECK-DT-INVALIDATE: Running analysis: DominatorTreeAnalysis23 24; RUN: opt < %s -passes='require<scalar-evolution>,invalidate<loops>,print<scalar-evolution>' \25; RUN: -debug-pass-manager -disable-output 2>&1 \26; RUN: | FileCheck %s -check-prefixes=CHECK,CHECK-LI-INVALIDATE27;28; CHECK-LI-INVALIDATE: Running pass: RequireAnalysisPass29; CHECK-LI-INVALIDATE: Running analysis: ScalarEvolutionAnalysis30; CHECK-LI-INVALIDATE: Running analysis: LoopAnalysis31; CHECK-LI-INVALIDATE: Running pass: InvalidateAnalysisPass32; CHECK-LI-INVALIDATE: Invalidating analysis: LoopAnalysis33; CHECK-LI-INVALIDATE: Running pass: ScalarEvolutionPrinterPass34; CHECK-LI-INVALIDATE: Running analysis: ScalarEvolutionAnalysis35; CHECK-LI-INVALIDATE: Running analysis: LoopAnalysis36 37; This test isn't particularly interesting, its just enough to make sure we38; actually do some work inside of SCEV so that if we regress here despite the39; debug pass printing continuing to match, ASan and other tools can catch it.40define void @test(i32 %n) {41; CHECK-LABEL: Classifying expressions for: @test42; CHECK: Loop %loop: backedge-taken count is i32 1443; CHECK: Loop %loop: constant max backedge-taken count is i32 1444 45entry:46 br label %loop47 48loop:49 %iv = phi i32 [ 0, %entry ], [ %iv.inc, %loop ]50 %iv.inc = add nsw i32 %iv, 351 %becond = icmp ne i32 %iv.inc, 4652 br i1 %becond, label %loop, label %leave53 54leave:55 ret void56}57