File: setcc-takes-i32.ll

package info (click to toggle)
llvm-toolchain-9 1%3A9.0.1-16
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 882,436 kB
  • sloc: cpp: 4,167,636; ansic: 714,256; asm: 457,610; python: 155,927; objc: 65,094; sh: 42,856; lisp: 26,908; perl: 7,786; pascal: 7,722; makefile: 6,881; ml: 5,581; awk: 3,648; cs: 2,027; xml: 888; javascript: 381; ruby: 156
file content (22 lines) | stat: -rw-r--r-- 904 bytes parent folder | download | duplicates (35)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
; RUN: llc -verify-machineinstrs -mtriple=aarch64-none-linux-gnu -o - %s | FileCheck %s

; Most important point here is that the promotion of the i1 works
; correctly. Previously LLVM thought that i64 was the appropriate SetCC output,
; which meant it proceded in two steps and produced an i64 -> i64 any_ext which
; couldn't be selected and faulted.

; It was expecting the smallest legal promotion of i1 to be the preferred SetCC
; type, so we'll satisfy it (this actually arguably gives better code anyway,
; with flag-manipulation operations allowed to use W-registers).

declare {i64, i1} @llvm.umul.with.overflow.i64(i64, i64)

define i64 @test_select(i64 %lhs, i64 %rhs) {
; CHECK-LABEL: test_select:

  %res = call {i64, i1} @llvm.umul.with.overflow.i64(i64 %lhs, i64 %rhs)
  %flag = extractvalue {i64, i1} %res, 1
  %retval = select i1 %flag, i64 %lhs, i64 %rhs
  ret i64 %retval
; CHECK: ret
}