File: stable_ir_values.ll

package info (click to toggle)
llvm-toolchain-21 1%3A21.1.6-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 2,245,028 kB
  • sloc: cpp: 7,619,726; ansic: 1,434,018; asm: 1,058,748; python: 252,740; f90: 94,671; objc: 70,685; lisp: 42,813; pascal: 18,401; sh: 8,601; ml: 5,111; perl: 4,720; makefile: 3,675; awk: 3,523; javascript: 2,409; xml: 892; fortran: 770
file content (22 lines) | stat: -rw-r--r-- 902 bytes parent folder | download | duplicates (10)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py UTC_ARGS: --version 3
; RUN: opt < %s -S | FileCheck %s

; The assumption underlying this test is that there are pre-existing check lines
; but something has changed, and we would like to avoid needless changes of
; meta variable names so that diffs end up being easier to read, e.g. avoid
; changing X_I33 into X_I34 or renumbering the various TMP variables.

define i32 @func({i32, i32} %x, i32 %y) {
; CHECK-LABEL: define i32 @func(
; CHECK-SAME: { i32, i32 } [[X:%.*]], i32 [[Y:%.*]]) {
; CHECK-NEXT:    [[X_I33:%.*]] = extractvalue { i32, i32 } [[X]], 0
; CHECK-NEXT:    [[TMP1:%.*]] = add i32 [[X_I33]], [[Y]]
; CHECK-NEXT:    [[TMP2:%.*]] = mul i32 [[TMP1]], 3
; CHECK-NEXT:    ret i32 [[TMP2]]
;
  %x.i34 = extractvalue {i32, i32} %x, 0
  %1 = add i32 %y, 1
  %2 = add i32 %x.i34, %1
  %3 = mul i32 %2, 3
  ret i32 %3
}