File: trivial-function-definition.ll

package info (click to toggle)
llvm-toolchain-20 1%3A20.1.6-1~exp1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 2,111,304 kB
  • sloc: cpp: 7,438,677; ansic: 1,393,822; asm: 1,012,926; python: 241,650; f90: 86,635; objc: 75,479; lisp: 42,144; pascal: 17,286; sh: 10,027; ml: 5,082; perl: 4,730; awk: 3,523; makefile: 3,349; javascript: 2,251; xml: 892; fortran: 672
file content (25 lines) | stat: -rw-r--r-- 909 bytes parent folder | download | duplicates (6) 
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 -verify-machineinstrs -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
}