File: invalidation.ll

package info (click to toggle)
llvm-toolchain-17 1%3A17.0.6-22
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,799,624 kB
  • sloc: cpp: 6,428,607; ansic: 1,383,196; asm: 793,408; python: 223,504; objc: 75,364; f90: 60,502; lisp: 33,869; pascal: 15,282; sh: 9,684; perl: 7,453; ml: 4,937; awk: 3,523; makefile: 2,889; javascript: 2,149; xml: 888; fortran: 619; cs: 573
file content (64 lines) | stat: -rw-r--r-- 2,781 bytes parent folder | download | duplicates (10)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
; Test that access-info gets invalidated when the analyses it depends on are
; invalidated.

; This is a reproducer for https://github.com/llvm/llvm-project/issues/61324.
; We want to see that LoopAccessAnalysis+AAManger is being updated at the end,
; instead of crashing when using a stale AAManager.
;
; RUN: opt < %s -disable-output -debug-pass-manager -passes='function(require<access-info>,invalidate<aa>),print<access-info>' 2>&1 | FileCheck %s --check-prefix=CHECK-AA
;
; CHECK-AA: Running pass: RequireAnalysisPass
; CHECK-AA-NEXT: Running analysis: LoopAccessAnalysis on foo
; CHECK-AA: Running pass: InvalidateAnalysisPass
; CHECK-AA-NEXT: Invalidating analysis: AAManager on foo
; CHECK-AA-NEXT: Invalidating analysis: LoopAccessAnalysis on foo
; CHECK-AA-NEXT: Running pass: LoopAccessInfoPrinterPass on foo
; CHECK-AA-NEXT: Running analysis: LoopAccessAnalysis on foo
; CHECK-AA-NEXT: Running analysis: AAManager on foo


; Verify that an explicit invalidate request for access-info result in an
; invalidation.
;
; RUN: opt < %s -disable-output -debug-pass-manager -passes='function(require<access-info>,invalidate<access-info>)' 2>&1 | FileCheck %s --check-prefix=CHECK-INV-AA
;
; CHECK-INV-AA: Running pass: RequireAnalysisPass
; CHECK-INV-AA-NEXT: Running analysis: LoopAccessAnalysis on foo
; CHECK-INV-AA: Running pass: InvalidateAnalysisPass
; CHECK-INV-AA-NEXT: Invalidating analysis: LoopAccessAnalysis on foo


; Invalidation of scalar-evolution should transitively invalidate access-info.
;
; RUN: opt < %s -disable-output -debug-pass-manager -passes='function(require<access-info>,invalidate<scalar-evolution>)' 2>&1 | FileCheck %s --check-prefix=CHECK-SCEV
;
; CHECK-SCEV: Running pass: RequireAnalysisPass
; CHECK-SCEV-NEXT: Running analysis: LoopAccessAnalysis on foo
; CHECK-SCEV: Running pass: InvalidateAnalysisPass
; CHECK-SCEV-NEXT: Invalidating analysis: ScalarEvolutionAnalysis on foo
; CHECK-SCEV-NEXT: Invalidating analysis: LoopAccessAnalysis on foo


; Invalidation of domtree should transitively invalidate access-info.
;
; RUN: opt < %s -disable-output -debug-pass-manager -passes='function(require<access-info>,invalidate<domtree>)' 2>&1 | FileCheck %s --check-prefix=CHECK-DT
;
; CHECK-DT: Running pass: RequireAnalysisPass
; CHECK-DT-NEXT: Running analysis: LoopAccessAnalysis on foo
; CHECK-DT: Running pass: InvalidateAnalysisPass
; CHECK-DT-NEXT: Invalidating analysis: DominatorTreeAnalysis on foo
; CHECK-DT: Invalidating analysis: LoopAccessAnalysis on foo


define void @foo(ptr nocapture writeonly %a, ptr nocapture writeonly %b) memory(argmem: write) {
entry:
  br label %for.cond1

for.cond1:
  store i16 0, ptr %b, align 1
  store i16 0, ptr %a, align 1
  br i1 true, label %for.end6, label %for.cond1

for.end6:
  ret void
}