File: stable_ir_values.ll.expected.reset

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 (23 lines) | stat: -rw-r--r-- 954 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
23
 
; 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_I34:%.*]] = extractvalue { i32, i32 } [[X]], 0
; CHECK-NEXT:    [[TMP1:%.*]] = add i32 [[Y]], 1
; CHECK-NEXT:    [[TMP2:%.*]] = add i32 [[X_I34]], [[TMP1]]
; CHECK-NEXT:    [[TMP3:%.*]] = mul i32 [[TMP2]], 3
; CHECK-NEXT:    ret i32 [[TMP3]]
;
  %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
}