File: module-inlining.ll

package info (click to toggle)
llvm-toolchain-20 1%3A20.1.8-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 2,111,696 kB
  • sloc: cpp: 7,438,781; ansic: 1,393,871; asm: 1,012,926; python: 241,771; f90: 86,635; objc: 75,411; lisp: 42,144; pascal: 17,286; sh: 8,596; ml: 5,082; perl: 4,730; makefile: 3,591; awk: 3,523; javascript: 2,251; xml: 892; fortran: 672
file content (28 lines) | stat: -rw-r--r-- 1,074 bytes parent folder | download | duplicates (17) 
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
 
; modify_value will be inlined into main. With just the inliner pass, at most 
; some trivial DCE would happen, which in this case doesn't modify post-inlined
; main much.
; In contrast, with the full set of module inliner-related passes, at the end of
; inlining (incl. function cleanups ran after inlining), main will be reduced to
; a 'ret 10'
;
; RUN: opt -passes=inline -S < %s | FileCheck %s --check-prefix=INLINE --check-prefix=CHECK
; RUN: opt -passes=inliner-wrapper -S < %s | FileCheck %s --check-prefix=INLINE --check-prefix=CHECK
; RUN: opt -passes=scc-oz-module-inliner -S < %s | FileCheck %s --check-prefix=MODULE --check-prefix=CHECK

define void @modify_value(ptr %v) {
    %f = getelementptr { i32, float }, ptr %v, i64 0, i32 0
    store i32 10, ptr %f
    ret void
}

define i32 @main() {
    %my_val = alloca {i32, float}
    call void @modify_value(ptr %my_val)
    %f = getelementptr { i32, float }, ptr %my_val, i64 0, i32 0
    %ret = load i32, ptr %f
    ret i32 %ret
}

; CHECK-LABEL: @main
; INLINE-NEXT: %my_val = alloca
; MODULE-NEXT: ret i32 10