2caaec65c0
Due to an improvement to name preservation, a lot of InstCombine tests now show spurious diffs when regenerated. Rather than regenerating individual files when they get touched, mass-regenerate all UTC-based InstCombine tests. I have then reset a number of files showing suspicious diffs where the UTC output has clearly been manually adjusted. I apologize if I missed anything in the mass of changes.
26 lines
757 B
LLVM
26 lines
757 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
|
|
; RUN: opt < %s -passes=instcombine -S | FileCheck %s
|
|
|
|
; Convert the zext+slt into a simple ult.
|
|
|
|
define i1 @scalar_zext_slt(i16 %t4) {
|
|
; CHECK-LABEL: @scalar_zext_slt(
|
|
; CHECK-NEXT: [[T6:%.*]] = icmp ult i16 [[T4:%.*]], 500
|
|
; CHECK-NEXT: ret i1 [[T6]]
|
|
;
|
|
%t5 = zext i16 %t4 to i32
|
|
%t6 = icmp slt i32 %t5, 500
|
|
ret i1 %t6
|
|
}
|
|
|
|
define <4 x i1> @vector_zext_slt(<4 x i16> %t4) {
|
|
; CHECK-LABEL: @vector_zext_slt(
|
|
; CHECK-NEXT: [[T6:%.*]] = icmp ult <4 x i16> [[T4:%.*]], <i16 500, i16 0, i16 501, i16 -1>
|
|
; CHECK-NEXT: ret <4 x i1> [[T6]]
|
|
;
|
|
%t5 = zext <4 x i16> %t4 to <4 x i32>
|
|
%t6 = icmp slt <4 x i32> %t5, <i32 500, i32 0, i32 501, i32 65535>
|
|
ret <4 x i1> %t6
|
|
}
|
|
|