File: trivial-function-definition.ll

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-proposed-updates
  • size: 1,998,492 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (25 lines) | stat: -rw-r--r-- 887 bytes parent folder | download | duplicates (8) 
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
 
; RUN: llc -O0 -mtriple=spirv32-unknown-unknown %s -o - | FileCheck %s

;; Debug info:
; CHECK:     OpName %[[#FOO:]] "foo"

;; Types:
; CHECK:     %[[#VOID:]] = OpTypeVoid
; CHECK:     %[[#FN:]] = OpTypeFunction %[[#VOID]]

;; Functions:
; CHECK:     %[[#FOO]] = OpFunction %[[#VOID]] None %[[#FN]]
; CHECK-NOT: OpFunctionParameter
;; NOTE: In 2.4, it isn't explicitly written that a function always has a least
;;       one block. In fact, 2.4.11 seems to imply that there are at least two
;;       blocks in functions with a body, but that doesn't make much sense.
;;       However, in order to distinguish between function declaration and
;;       definition, a function needs at least one block, hence why this test
;;       expects one OpLabel + OpReturn.
; CHECK:     OpLabel
; CHECK:     OpReturn
; CHECK-NOT: OpLabel
; CHECK:     OpFunctionEnd
define void @foo() {
  ret void
}