1 ; RUN: llc < %s -mtriple=arm-apple-darwin | FileCheck %s
2 ; RUN: llc < %s -march=arm -mattr=+vfp2 | FileCheck %s --check-prefix=CHECK-VFP
3 ; RUN: llc < %s -mattr=+neon,+thumb2 -mtriple=thumbv7-apple-darwin | FileCheck %s --check-prefix=CHECK-NEON
5 define i32 @f1(i32 %a.s) {
9 %tmp = icmp eq i32 %a.s, 4
10 %tmp1.s = select i1 %tmp, i32 2, i32 3
14 define i32 @f2(i32 %a.s) {
18 %tmp = icmp sgt i32 %a.s, 4
19 %tmp1.s = select i1 %tmp, i32 2, i32 3
23 define i32 @f3(i32 %a.s, i32 %b.s) {
27 %tmp = icmp slt i32 %a.s, %b.s
28 %tmp1.s = select i1 %tmp, i32 2, i32 3
32 define i32 @f4(i32 %a.s, i32 %b.s) {
36 %tmp = icmp sle i32 %a.s, %b.s
37 %tmp1.s = select i1 %tmp, i32 2, i32 3
41 define i32 @f5(i32 %a.u, i32 %b.u) {
45 %tmp = icmp ule i32 %a.u, %b.u
46 %tmp1.s = select i1 %tmp, i32 2, i32 3
50 define i32 @f6(i32 %a.u, i32 %b.u) {
54 %tmp = icmp ugt i32 %a.u, %b.u
55 %tmp1.s = select i1 %tmp, i32 2, i32 3
59 define double @f7(double %a, double %b) {
65 %tmp = fcmp olt double %a, 1.234e+00
66 %tmp1 = select i1 %tmp, double -1.000e+00, double %b
70 ; <rdar://problem/7260094>
72 ; We used to generate really horrible code for this function. The main cause was
73 ; a lack of a custom lowering routine for an ISD::SELECT. This would result in
74 ; two "it" blocks in the code: one for the "icmp" and another to move the index
75 ; into the constant pool based on the value of the "icmp". If we have one "it"
76 ; block generated, odds are good that we have close to the ideal code for this:
79 ; CHECK-NEON: movw [[REGISTER_1:r[0-9]+]], #1123
80 ; CHECK-NEON-NEXT: movs [[REGISTER_2:r[0-9]+]], #0
81 ; CHECK-NEON-NEXT: cmp r0, [[REGISTER_1]]
82 ; CHECK-NEON-NEXT: it eq
83 ; CHECK-NEON-NEXT: moveq [[REGISTER_2]], #4
84 ; CHECK-NEON-NEXT: adr [[REGISTER_3:r[0-9]+]], #LCPI
85 ; CHECK-NEON-NEXT: ldr
88 define arm_apcscc float @f8(i32 %a) nounwind {
89 %tmp = icmp eq i32 %a, 1123
90 %tmp1 = select i1 %tmp, float 0x3FF3BE76C0000000, float 0x40030E9A20000000
94 ; <rdar://problem/9049552>
95 ; Glue values can only have a single use, but the following test exposed a
96 ; case where a SELECT was lowered with 2 uses of a comparison, causing the
97 ; scheduler to assert.
100 declare i8* @objc_msgSend(i8*, i8*, ...)
101 define void @f9() optsize {
103 %cmp = icmp eq i8* undef, inttoptr (i32 4 to i8*)
104 %conv191 = select i1 %cmp, float -3.000000e+00, float 0.000000e+00
105 %conv195 = select i1 %cmp, double -1.000000e+00, double 0.000000e+00
106 %add = fadd double %conv195, 1.100000e+01
107 %conv196 = fptrunc double %add to float
108 %add201 = fadd float undef, %conv191
109 %tmp484 = bitcast float %conv196 to i32
110 %tmp478 = bitcast float %add201 to i32
111 %tmp490 = insertvalue [2 x i32] undef, i32 %tmp484, 0
112 %tmp493 = insertvalue [2 x i32] %tmp490, i32 %tmp478, 1
113 call void bitcast (i8* (i8*, i8*, ...)* @objc_msgSend to void (i8*, i8*, [2 x i32], i32, float)*)(i8* undef, i8* undef, [2 x i32] %tmp493, i32 0, float 1.000000e+00) optsize