2017-03-01 22:41:57 +08:00
|
|
|
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
2009-12-15 08:41:36 +08:00
|
|
|
; RUN: llc < %s -mtriple=x86_64-apple-darwin | FileCheck %s
|
2009-12-15 08:53:42 +08:00
|
|
|
; rdar://7329206
|
|
|
|
|
|
|
|
; Use sbb x, x to materialize carry bit in a GPR. The value is either
|
|
|
|
; all 1's or all 0's.
|
2009-12-15 08:41:36 +08:00
|
|
|
|
|
|
|
define zeroext i16 @t1(i16 zeroext %x) nounwind readnone ssp {
|
2013-07-14 14:24:09 +08:00
|
|
|
; CHECK-LABEL: t1:
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK: ## BB#0:
|
|
|
|
; CHECK-NEXT: xorl %eax, %eax
|
|
|
|
; CHECK-NEXT: cmpl $26, %edi
|
|
|
|
; CHECK-NEXT: seta %al
|
|
|
|
; CHECK-NEXT: shll $5, %eax
|
|
|
|
; CHECK-NEXT: retq
|
|
|
|
%t0 = icmp ugt i16 %x, 26
|
|
|
|
%if = select i1 %t0, i16 32, i16 0
|
|
|
|
ret i16 %if
|
2009-12-15 08:41:36 +08:00
|
|
|
}
|
|
|
|
|
2009-12-15 08:53:42 +08:00
|
|
|
define zeroext i16 @t2(i16 zeroext %x) nounwind readnone ssp {
|
2013-07-14 14:24:09 +08:00
|
|
|
; CHECK-LABEL: t2:
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK: ## BB#0:
|
2017-03-13 02:28:48 +08:00
|
|
|
; CHECK-NEXT: xorl %eax, %eax
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK-NEXT: cmpl $26, %edi
|
2017-03-13 02:28:48 +08:00
|
|
|
; CHECK-NEXT: setb %al
|
|
|
|
; CHECK-NEXT: shll $5, %eax
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK-NEXT: retq
|
|
|
|
%t0 = icmp ult i16 %x, 26
|
|
|
|
%if = select i1 %t0, i16 32, i16 0
|
|
|
|
ret i16 %if
|
2009-12-15 08:53:42 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
define i64 @t3(i64 %x) nounwind readnone ssp {
|
2013-07-14 14:24:09 +08:00
|
|
|
; CHECK-LABEL: t3:
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK: ## BB#0:
|
2017-03-13 02:28:48 +08:00
|
|
|
; CHECK-NEXT: xorl %eax, %eax
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK-NEXT: cmpq $18, %rdi
|
2017-03-13 02:28:48 +08:00
|
|
|
; CHECK-NEXT: setb %al
|
|
|
|
; CHECK-NEXT: shlq $6, %rax
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK-NEXT: retq
|
|
|
|
%t0 = icmp ult i64 %x, 18
|
|
|
|
%if = select i1 %t0, i64 64, i64 0
|
|
|
|
ret i64 %if
|
2009-12-15 08:53:42 +08:00
|
|
|
}
|
2015-08-20 17:00:56 +08:00
|
|
|
|
|
|
|
@v4 = common global i32 0, align 4
|
|
|
|
|
|
|
|
define i32 @t4(i32 %a) {
|
|
|
|
; CHECK-LABEL: t4:
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK: ## BB#0:
|
|
|
|
; CHECK-NEXT: movq _v4@{{.*}}(%rip), %rax
|
|
|
|
; CHECK-NEXT: cmpl $1, (%rax)
|
2017-03-02 06:51:31 +08:00
|
|
|
; CHECK-NEXT: movw $1, %ax
|
|
|
|
; CHECK-NEXT: adcw $0, %ax
|
|
|
|
; CHECK-NEXT: shll $16, %eax
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK-NEXT: retq
|
|
|
|
%t0 = load i32, i32* @v4, align 4
|
|
|
|
%not.tobool = icmp eq i32 %t0, 0
|
2015-08-20 17:00:56 +08:00
|
|
|
%conv.i = sext i1 %not.tobool to i16
|
|
|
|
%call.lobit = lshr i16 %conv.i, 15
|
|
|
|
%add.i.1 = add nuw nsw i16 %call.lobit, 1
|
|
|
|
%conv4.2 = zext i16 %add.i.1 to i32
|
|
|
|
%add = shl nuw nsw i32 %conv4.2, 16
|
|
|
|
ret i32 %add
|
|
|
|
}
|
[X86] Use the right type when folding xor (truncate (shift)) -> setcc
The result type of setcc is dependent on whether or not AVX512 is
present.
We had an X86-specific DAG-combine which assumed that the result type
should be i8 when it could be i1.
This meant that we would generate illegal setccs which LowerSETCC did
not like.
Instead, use an appropriate type and zero extend to i8.
Also, there were some scenarios where the fold should have fired but
didn't because we were overly cautious about the types. This meant that
we generated:
shrl $31, %edi
andl $1, %edi
kmovw %edi, %k0
kxnorw %k0, %k0, %k1
kshiftrw $15, %k1, %k1
kxorw %k1, %k0, %k0
kmovw %k0, %eax
instead of:
testl %edi, %edi
setns %al
This fixes PR27638.
llvm-svn: 268609
2016-05-05 14:00:56 +08:00
|
|
|
|
|
|
|
define i8 @t5(i32 %a) #0 {
|
|
|
|
; CHECK-LABEL: t5:
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK: ## BB#0:
|
|
|
|
; CHECK-NEXT: testl %edi, %edi
|
|
|
|
; CHECK-NEXT: setns %al
|
|
|
|
; CHECK-NEXT: retq
|
[X86] Use the right type when folding xor (truncate (shift)) -> setcc
The result type of setcc is dependent on whether or not AVX512 is
present.
We had an X86-specific DAG-combine which assumed that the result type
should be i8 when it could be i1.
This meant that we would generate illegal setccs which LowerSETCC did
not like.
Instead, use an appropriate type and zero extend to i8.
Also, there were some scenarios where the fold should have fired but
didn't because we were overly cautious about the types. This meant that
we generated:
shrl $31, %edi
andl $1, %edi
kmovw %edi, %k0
kxnorw %k0, %k0, %k1
kshiftrw $15, %k1, %k1
kxorw %k1, %k0, %k0
kmovw %k0, %eax
instead of:
testl %edi, %edi
setns %al
This fixes PR27638.
llvm-svn: 268609
2016-05-05 14:00:56 +08:00
|
|
|
%.lobit = lshr i32 %a, 31
|
|
|
|
%trunc = trunc i32 %.lobit to i8
|
|
|
|
%.not = xor i8 %trunc, 1
|
|
|
|
ret i8 %.not
|
|
|
|
}
|
|
|
|
|
|
|
|
define zeroext i1 @t6(i32 %a) #0 {
|
|
|
|
; CHECK-LABEL: t6:
|
2016-09-15 04:21:28 +08:00
|
|
|
; CHECK: ## BB#0:
|
|
|
|
; CHECK-NEXT: testl %edi, %edi
|
|
|
|
; CHECK-NEXT: setns %al
|
|
|
|
; CHECK-NEXT: retq
|
[X86] Use the right type when folding xor (truncate (shift)) -> setcc
The result type of setcc is dependent on whether or not AVX512 is
present.
We had an X86-specific DAG-combine which assumed that the result type
should be i8 when it could be i1.
This meant that we would generate illegal setccs which LowerSETCC did
not like.
Instead, use an appropriate type and zero extend to i8.
Also, there were some scenarios where the fold should have fired but
didn't because we were overly cautious about the types. This meant that
we generated:
shrl $31, %edi
andl $1, %edi
kmovw %edi, %k0
kxnorw %k0, %k0, %k1
kshiftrw $15, %k1, %k1
kxorw %k1, %k0, %k0
kmovw %k0, %eax
instead of:
testl %edi, %edi
setns %al
This fixes PR27638.
llvm-svn: 268609
2016-05-05 14:00:56 +08:00
|
|
|
%.lobit = lshr i32 %a, 31
|
|
|
|
%trunc = trunc i32 %.lobit to i1
|
|
|
|
%.not = xor i1 %trunc, 1
|
|
|
|
ret i1 %.not
|
|
|
|
}
|
|
|
|
|
|
|
|
attributes #0 = { "target-cpu"="skylake-avx512" }
|