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
|
;; Ensure that the MergeFunctions pass creates thunks with the appropriate debug
;; info format set (which would otherwise assert when inlining those thunks).
; RUN: opt -S -passes=mergefunc,inline --try-experimental-debuginfo-iterators < %s | FileCheck %s
declare void @f1()
declare void @f2()
define void @f3() {
call void @f1()
call void @f2()
ret void
}
;; MergeFunctions will replace f4 with a thunk that calls f3. Inlining will
;; inline f3 into that thunk, which would assert if the thunk had the incorrect
;; debug info format.
define void @f4() {
call void @f1()
call void @f2()
ret void
}
; CHECK-LABEL: define void @f4() {
; CHECK-NEXT: call void @f1()
; CHECK-NEXT: call void @f2()
; CHECK-NEXT: ret void
; CHECK-NEXT: }
;; Both of these are interposable, so MergeFunctions will create a common thunk
;; that both will call. Inlining will inline that thunk back, which would assert
;; if the thunk had the incorrect debug info format.
define weak void @f5() {
call void @f2()
call void @f1()
ret void
}
define weak void @f6() {
call void @f2()
call void @f1()
ret void
}
; CHECK-LABEL: define weak void @f6() {
; CHECK-NEXT: call void @f2()
; CHECK-NEXT: call void @f1()
; CHECK-NEXT: ret void
; CHECK-NEXT: }
; CHECK-LABEL: define weak void @f5() {
; CHECK-NEXT: call void @f2()
; CHECK-NEXT: call void @f1()
; CHECK-NEXT: ret void
; CHECK-NEXT: }
|
