File: setcc-takes-i32.ll

package info (click to toggle)
llvm-toolchain-7 1%3A7.0.1-8
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 733,456 kB
  • sloc: cpp: 3,776,651; ansic: 633,271; asm: 350,301; python: 142,716; objc: 107,612; sh: 22,626; lisp: 11,056; perl: 7,999; pascal: 6,742; ml: 5,537; awk: 3,536; makefile: 2,557; cs: 2,027; xml: 841; ruby: 156
file content (22 lines) | stat: -rw-r--r-- 904 bytes parent folder | download | duplicates (38)
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
}