File: metadata-function-blocks.ll

package info (click to toggle)
llvm-toolchain-14 1%3A14.0.6-12
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,496,180 kB
  • sloc: cpp: 5,593,972; ansic: 986,872; asm: 585,869; python: 184,223; objc: 72,530; lisp: 31,119; f90: 27,793; javascript: 9,780; pascal: 9,762; sh: 9,482; perl: 7,468; ml: 5,432; awk: 3,523; makefile: 2,538; xml: 953; cs: 573; fortran: 567
file content (78 lines) | stat: -rw-r--r-- 2,207 bytes parent folder | download | duplicates (28)
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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
; RUN: llvm-as < %s -bitcode-mdindex-threshold=0 | llvm-bcanalyzer -dump | FileCheck %s
; Test that metadata only used by a single function is serialized in that
; function instead of in the global pool.
;
; In order to make the bitcode records easy to follow, nodes in this testcase
; are named after the ids they are given in the bitcode.  Nodes local to a
; function have offsets of 100 or 200 (depending on the function) so that they
; remain unique within this textual IR.

; Check for strings in the global pool.
; CHECK:      <METADATA_BLOCK
; CHECK-NEXT:   <STRINGS
; CHECK-SAME:           /> num-strings = 3 {
; CHECK-NEXT:     'named'
; CHECK-NEXT:     'named and foo'
; CHECK-NEXT:     'foo and bar'
; CHECK-NEXT:   }

; Each node gets a new number.  Bottom-up traversal of nodes.
!named = !{!6}

; Before the records we emit an offset to the index for the block
; CHECK-NEXT:   <INDEX_OFFSET

; CHECK-NEXT:   <NODE op0=1/>
!4 = !{!"named"}

; CHECK-NEXT:   <NODE op0=2/>
!5 = !{!"named and foo"}

; CHECK-NEXT:   <NODE op0=1 op1=4 op2=5/>
!6 = !{!"named", !4, !5}

; CHECK-NEXT:   <NODE op0=3/>
!7 = !{!"foo and bar"}

; CHECK-NOT:    <NODE
; CHECK:      </METADATA_BLOCK

; Look at metadata local to @foo, starting with strings.
; CHECK:      <FUNCTION_BLOCK
; CHECK:        <METADATA_BLOCK
; CHECK-NEXT:     <STRINGS
; CHECK-SAME:             /> num-strings = 1 {
; CHECK-NEXT:       'foo'
; CHECK-NEXT:     }

; Function-local nodes start at 9 (strings at 8).
; CHECK-NEXT:     <NODE op0=8/>
!109 = !{!"foo"}

; CHECK-NEXT:     <NODE op0=8 op1=3 op2=9 op3=7 op4=5/>
!110 = !{!"foo", !"foo and bar", !109, !7, !5}

; CHECK-NEXT:   </METADATA_BLOCK
define void @foo() !foo !110 {
  unreachable
}

; Look at metadata local to @bar, starting with strings.
; CHECK:    <FUNCTION_BLOCK
; CHECK:      <METADATA_BLOCK
; CHECK-NEXT:   <STRINGS
; CHECK-SAME:           /> num-strings = 1 {
; CHECK-NEXT:     'bar'
; CHECK-NEXT:   }

; Function-local nodes start at 9 (strings at 8).
; CHECK-NEXT:   <NODE op0=8/>
!209 = !{!"bar"}

; CHECK-NEXT:   <NODE op0=8 op1=3 op2=9 op3=7/>
!210 = !{!"bar", !"foo and bar", !209, !7}

; CHECK-NEXT: </METADATA_BLOCK
define void @bar() {
  unreachable, !bar !210
}