1; RUN: llc -mtriple=aarch64-none-linux-gnu -verify-machineinstrs < %s | FileCheck %s
2
3; LLVM should be able to cope with multiple uses of the same flag-setting
4; instruction at different points of a routine. Either by rematerializing the
5; compare or by saving and restoring the flag register.
6
7declare void @bar()
8
9@var = global i32 0
10
11define i32 @test_multiflag(i32 %n, i32 %m, i32 %o) {
12; CHECK-LABEL: test_multiflag:
13
14  %test = icmp ne i32 %n, %m
15; CHECK: cmp [[LHS:w[0-9]+]], [[RHS:w[0-9]+]]
16
17  %val = zext i1 %test to i32
18; CHECK: csinc {{[xw][0-9]+}}, {{xzr|wzr}}, {{xzr|wzr}}, eq
19
20  store i32 %val, i32* @var
21
22  call void @bar()
23; CHECK: bl bar
24
25  ; Currently, the comparison is emitted again. An MSR/MRS pair would also be
26  ; acceptable, but assuming the call preserves NZCV is not.
27  br i1 %test, label %iftrue, label %iffalse
28; CHECK: cmp [[LHS]], [[RHS]]
29; CHECK: b.eq
30
31iftrue:
32  ret i32 42
33iffalse:
34  ret i32 0
35}
36