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 it
4; due to a dependency being invalidated, and then re-urns it. This will
5; directly fail and indicates a failure that would occur later if we ddidn't
6; 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<assumptions>,print<scalar-evolution>' \
12; RUN:     -debug-pass-manager -disable-output 2>&1 \
13; RUN:     | FileCheck %s -check-prefixes=CHECK,CHECK-AC-INVALIDATE
14;
15; CHECK-AC-INVALIDATE: Running pass: RequireAnalysisPass
16; CHECK-AC-INVALIDATE: Running analysis: ScalarEvolutionAnalysis
17; CHECK-AC-INVALIDATE: Running analysis: AssumptionAnalysis
18; CHECK-AC-INVALIDATE: Running pass: InvalidateAnalysisPass
19; CHECK-AC-INVALIDATE: Invalidating analysis: AssumptionAnalysis
20; CHECK-AC-INVALIDATE: Running pass: ScalarEvolutionPrinterPass
21; CHECK-AC-INVALIDATE: Running analysis: ScalarEvolutionAnalysis
22; CHECK-AC-INVALIDATE: Running analysis: AssumptionAnalysis
23
24; RUN: opt < %s -passes='require<scalar-evolution>,invalidate<domtree>,print<scalar-evolution>' \
25; RUN:     -debug-pass-manager -disable-output 2>&1 \
26; RUN:     | FileCheck %s -check-prefixes=CHECK,CHECK-DT-INVALIDATE
27;
28; CHECK-DT-INVALIDATE: Running pass: RequireAnalysisPass
29; CHECK-DT-INVALIDATE: Running analysis: ScalarEvolutionAnalysis
30; CHECK-DT-INVALIDATE: Running analysis: DominatorTreeAnalysis
31; CHECK-DT-INVALIDATE: Running pass: InvalidateAnalysisPass
32; CHECK-DT-INVALIDATE: Invalidating analysis: DominatorTreeAnalysis
33; CHECK-DT-INVALIDATE: Running pass: ScalarEvolutionPrinterPass
34; CHECK-DT-INVALIDATE: Running analysis: ScalarEvolutionAnalysis
35; CHECK-DT-INVALIDATE: Running analysis: DominatorTreeAnalysis
36
37; RUN: opt < %s -passes='require<scalar-evolution>,invalidate<loops>,print<scalar-evolution>' \
38; RUN:     -debug-pass-manager -disable-output 2>&1 \
39; RUN:     | FileCheck %s -check-prefixes=CHECK,CHECK-LI-INVALIDATE
40;
41; CHECK-LI-INVALIDATE: Running pass: RequireAnalysisPass
42; CHECK-LI-INVALIDATE: Running analysis: ScalarEvolutionAnalysis
43; CHECK-LI-INVALIDATE: Running analysis: LoopAnalysis
44; CHECK-LI-INVALIDATE: Running pass: InvalidateAnalysisPass
45; CHECK-LI-INVALIDATE: Invalidating analysis: LoopAnalysis
46; CHECK-LI-INVALIDATE: Running pass: ScalarEvolutionPrinterPass
47; CHECK-LI-INVALIDATE: Running analysis: ScalarEvolutionAnalysis
48; CHECK-LI-INVALIDATE: Running analysis: LoopAnalysis
49
50; This test isn't particularly interesting, its just enough to make sure we
51; actually do some work inside of SCEV so that if we regress here despite the
52; debug pass printing continuing to match, ASan and other tools can catch it.
53define void @test(i32 %n) {
54; CHECK-LABEL: Classifying expressions for: @test
55; CHECK: Loop %loop: backedge-taken count is 14
56; CHECK: Loop %loop: max backedge-taken count is 14
57; CHECK: Loop %loop: Predicated backedge-taken count is 14
58
59entry:
60  br label %loop
61
62loop:
63  %iv = phi i32 [ 0, %entry ], [ %iv.inc, %loop ]
64  %iv.inc = add nsw i32 %iv, 3
65  %becond = icmp ne i32 %iv.inc, 46
66  br i1 %becond, label %loop, label %leave
67
68leave:
69  ret void
70}
71