File: setcc-takes-i32.ll

package info (click to toggle)
llvm-toolchain-4.0 1%3A4.0.1-10~deb9u2
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 493,332 kB
  • sloc: cpp: 2,698,100; ansic: 552,773; asm: 128,821; python: 121,589; objc: 105,054; sh: 21,174; lisp: 6,758; ml: 5,532; perl: 5,311; pascal: 5,245; makefile: 2,083; cs: 1,868; xml: 686; php: 212; csh: 117
file content (22 lines) | stat: -rw-r--r-- 904 bytes parent folder | download | duplicates (44)
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
}