maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Analysis/Dominators/basic.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

61 lines
1.1 KiB
LLVM
Raw Normal View History

[PM] Port domtree to the new pass manager (at last). This adds the domtree analysis to the new pass manager. The analysis returns the same DominatorTree result entity used by the old pass manager and essentially all of the code is shared. We just have different boilerplate for running and printing the analysis. I've converted one test to run in both modes just to make sure this is exercised while both are live in the tree. llvm-svn: 225969
2015-01-14 18:19:28 +08:00
; RUN: opt < %s -domtree -analyze | FileCheck %s -check-prefix=CHECK -check-prefix=CHECK-OLDPM
; RUN: opt < %s -disable-output -passes='print<domtree>' 2>&1 | FileCheck %s -check-prefix=CHECK -check-prefix=CHECK-NEWPM
[dom] Add a basic dominator tree test. Correct, we have *zero* basic testing of the dominator tree in the regression test suite. There is a single test that even prints it out, and that test only checks a single line of the output. There are a handful of tests that check post dominators, but all of those are looking for bugs rather than just exercising the basic machinery. This test is super boring and unexciting. But hey, it's something. I needed there to be something so I could switch the basic test to run with both the old and new pass manager. llvm-svn: 225936
2015-01-14 11:34:55 +08:00
define void @test1() {
[PM] Port domtree to the new pass manager (at last). This adds the domtree analysis to the new pass manager. The analysis returns the same DominatorTree result entity used by the old pass manager and essentially all of the code is shared. We just have different boilerplate for running and printing the analysis. I've converted one test to run in both modes just to make sure this is exercised while both are live in the tree. llvm-svn: 225969
2015-01-14 18:19:28 +08:00
; CHECK-OLDPM-LABEL: 'Dominator Tree Construction' for function 'test1':
; CHECK-NEWPM-LABEL: DominatorTree for function: test1
[dom] Add a basic dominator tree test. Correct, we have *zero* basic testing of the dominator tree in the regression test suite. There is a single test that even prints it out, and that test only checks a single line of the output. There are a handful of tests that check post dominators, but all of those are looking for bugs rather than just exercising the basic machinery. This test is super boring and unexciting. But hey, it's something. I needed there to be something so I could switch the basic test to run with both the old and new pass manager. llvm-svn: 225936
2015-01-14 11:34:55 +08:00
; CHECK: [1] %entry
; CHECK-NEXT: [2] %a
; CHECK-NEXT: [2] %c
; CHECK-NEXT: [3] %d
; CHECK-NEXT: [3] %e
; CHECK-NEXT: [2] %b
entry:
br i1 undef, label %a, label %b
a:
br label %c
b:
br label %c
c:
br i1 undef, label %d, label %e
d:
ret void
e:
ret void
}
define void @test2() {
[PM] Port domtree to the new pass manager (at last). This adds the domtree analysis to the new pass manager. The analysis returns the same DominatorTree result entity used by the old pass manager and essentially all of the code is shared. We just have different boilerplate for running and printing the analysis. I've converted one test to run in both modes just to make sure this is exercised while both are live in the tree. llvm-svn: 225969
2015-01-14 18:19:28 +08:00
; CHECK-OLDPM-LABEL: 'Dominator Tree Construction' for function 'test2':
; CHECK-NEWPM-LABEL: DominatorTree for function: test2
[dom] Add a basic dominator tree test. Correct, we have *zero* basic testing of the dominator tree in the regression test suite. There is a single test that even prints it out, and that test only checks a single line of the output. There are a handful of tests that check post dominators, but all of those are looking for bugs rather than just exercising the basic machinery. This test is super boring and unexciting. But hey, it's something. I needed there to be something so I could switch the basic test to run with both the old and new pass manager. llvm-svn: 225936
2015-01-14 11:34:55 +08:00
; CHECK: [1] %entry
; CHECK-NEXT: [2] %a
; CHECK-NEXT: [3] %b
; CHECK-NEXT: [4] %c
; CHECK-NEXT: [5] %d
; CHECK-NEXT: [5] %ret
entry:
br label %a
a:
br label %b
b:
br i1 undef, label %a, label %c
c:
br i1 undef, label %d, label %ret
d:
br i1 undef, label %a, label %ret
ret:
ret void
}