blob: cae6856d799e6e2032f753243e41bff55e616a7a [file] [log] [blame]
Tim Northovere3d42362013-02-01 11:40:47 +00001; RUN: llc -mtriple=aarch64-none-linux-gnu -verify-machineinstrs < %s | FileCheck %s
Tim Northoverbd668872014-04-15 14:00:29 +00002; RUN: llc -mtriple=arm64-none-linux-gnu -verify-machineinstrs -o - %s | FileCheck %s
Tim Northovere0e3aef2013-01-31 12:12:40 +00003
4; LLVM should be able to cope with multiple uses of the same flag-setting
5; instruction at different points of a routine. Either by rematerializing the
6; compare or by saving and restoring the flag register.
7
8declare void @bar()
9
10@var = global i32 0
11
12define i32 @test_multiflag(i32 %n, i32 %m, i32 %o) {
Stephen Linf799e3f2013-07-13 20:38:47 +000013; CHECK-LABEL: test_multiflag:
Tim Northovere0e3aef2013-01-31 12:12:40 +000014
15 %test = icmp ne i32 %n, %m
16; CHECK: cmp [[LHS:w[0-9]+]], [[RHS:w[0-9]+]]
17
18 %val = zext i1 %test to i32
Tim Northoveree20caa2014-05-12 18:04:06 +000019; CHECK: cset {{[xw][0-9]+}}, ne
Tim Northovere0e3aef2013-01-31 12:12:40 +000020
21 store i32 %val, i32* @var
22
23 call void @bar()
24; CHECK: bl bar
25
26 ; Currently, the comparison is emitted again. An MSR/MRS pair would also be
27 ; acceptable, but assuming the call preserves NZCV is not.
28 br i1 %test, label %iftrue, label %iffalse
29; CHECK: cmp [[LHS]], [[RHS]]
30; CHECK: b.eq
31
32iftrue:
33 ret i32 42
34iffalse:
35 ret i32 0
36}