File: fast-isel-br-i1.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 (48 lines) | stat: -rw-r--r-- 1,236 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
; RUN: llc < %s -fast-isel -asm-verbose=false -wasm-keep-registers | FileCheck %s

target datalayout = "e-m:e-p:32:32-i64:64-n32:64-S128"
target triple = "wasm32-unknown-unknown"

; Fast-isel uses a 32-bit xor with -1 to negate i1 values, because it doesn't
; make any guarantees about the contents of the high bits of a register holding
; an i1 value. Test that when we do a `br_if` or `br_unless` with what what an
; i1 value in LLVM IR, that we only test the low bit.

; CHECK: i32.xor
; CHECK: i32.const       $push[[L0:[0-9]+]]=, 1{{$}}
; CHECK: i32.and         $push[[L1:[0-9]+]]=, $pop{{[0-9]+}}, $pop[[L0]]{{$}}
; CHECK: br_if           0, $pop[[L1]]{{$}}

; CHECK: i32.xor
; CHECK: i32.const       $push[[L2:[0-9]+]]=, 1{{$}}
; CHECK: i32.and         $push[[L3:[0-9]+]]=, $pop{{[0-9]+}}, $pop[[L2]]{{$}}
; CHECK: br_if           0, $pop[[L3]]{{$}}

define void @test() {
start:
  %0 = call i32 @return_one()
  br label %bb1

bb1:
  %1 = icmp eq i32 %0, 1
  %2 = xor i1 %1, true
  br i1 %2, label %bb2, label %bb3

bb2:
  call void @panic()
  unreachable

bb3:
  %3 = xor i1 %2, true
  br i1 %3, label %bb4, label %bb5

bb4:
  call void @panic()
  unreachable

bb5:
  ret void
}

declare i32 @return_one()
declare void @panic()