c0e6b8ac3a
Just as as llvm IR supports explicitly specifying numeric value ids
for instructions, and emits them by default in textual output, now do
the same for blocks.
This is a slightly incompatible change in the textual IR format.
Previously, llvm would parse numeric labels as string names. E.g.
define void @f() {
br label %"55"
55:
ret void
}
defined a label *named* "55", even without needing to be quoted, while
the reference required quoting. Now, if you intend a block label which
looks like a value number to be a name, you must quote it in the
definition too (e.g. `"55":`).
Previously, llvm would print nameless blocks only as a comment, and
would omit it if there was no predecessor. This could cause confusion
for readers of the IR, just as unnamed instructions did prior to the
addition of "%5 = " syntax, back in 2008 (PR2480).
Now, it will always print a label for an unnamed block, with the
exception of the entry block. (IMO it may be better to print it for
the entry-block as well. However, that requires updating many more
tests.)
Thus, the following is supported, and is the canonical printing:
define i32 @f(i32, i32) {
%3 = add i32 %0, %1
br label %4
4:
ret i32 %3
}
New test cases covering this behavior are added, and other tests
updated as required.
Differential Revision: https://reviews.llvm.org/D58548
llvm-svn: 356789
51 lines
1.5 KiB
LLVM
51 lines
1.5 KiB
LLVM
; REQUIRES: asserts
|
|
; RUN: opt < %s -passes='print<domfrontier>' 2>&1 | FileCheck %s
|
|
|
|
define void @a_linear_impl_fig_1() nounwind {
|
|
0:
|
|
br label %1
|
|
1:
|
|
br label %2
|
|
2:
|
|
br label %3
|
|
3:
|
|
br i1 1, label %12, label %4
|
|
4:
|
|
br i1 1, label %5, label %1
|
|
5:
|
|
br i1 1, label %8, label %6
|
|
6:
|
|
br i1 1, label %7, label %4
|
|
7:
|
|
ret void
|
|
8:
|
|
br i1 1, label %9, label %1
|
|
9:
|
|
br label %10
|
|
10:
|
|
br i1 1, label %13, label %11
|
|
11:
|
|
br i1 1, label %9, label %8
|
|
12:
|
|
br i1 1, label %2, label %1
|
|
13:
|
|
switch i32 0, label %1 [ i32 0, label %9
|
|
i32 1, label %8]
|
|
}
|
|
|
|
; CHECK: DominanceFrontier for function: a_linear_impl_fig_1
|
|
; CHECK-DAG: DomFrontier for BB %0 is:
|
|
; CHECK-DAG: DomFrontier for BB %11 is: %{{[8|9]}} %{{[8|9]}}
|
|
; CHECK-DAG: DomFrontier for BB %1 is: %1
|
|
; CHECK-DAG: DomFrontier for BB %2 is: %{{[1|2]}} %{{[1|2]}}
|
|
; CHECK-DAG: DomFrontier for BB %3 is: %{{[1|2]}} %{{[1|2]}}
|
|
; CHECK-DAG: DomFrontier for BB %12 is: %{{[1|2]}} %{{[1|2]}}
|
|
; CHECK-DAG: DomFrontier for BB %4 is: %{{[1|4]}} %{{[1|4]}}
|
|
; CHECK-DAG: DomFrontier for BB %5 is: %{{[1|4]}} %{{[1|4]}}
|
|
; CHECK-DAG: DomFrontier for BB %8 is: %{{[1|8]}} %{{[1|8]}}
|
|
; CHECK-DAG: DomFrontier for BB %6 is: %4
|
|
; CHECK-DAG: DomFrontier for BB %7 is:
|
|
; CHECK-DAG: DomFrontier for BB %9 is: %{{[1|8|9]}} %{{[1|8|9]}} %{{[1|8|9]}}
|
|
; CHECK-DAG: DomFrontier for BB %10 is: %{{[1|8|9]}} %{{[1|8|9]}} %{{[1|8|9]}}
|
|
; CHECK-DAG: DomFrontier for BB %13 is: %{{[1|8|9]}} %{{[1|8|9]}} %{{[1|8|9]}}
|