maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/CodeGen/SystemZ/vec-min-03.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

84 lines
2.3 KiB
LLVM
Raw Normal View History

[SystemZ] Add CodeGen support for integer vector types This the first of a series of patches to add CodeGen support exploiting the instructions of the z13 vector facility. This patch adds support for the native integer vector types (v16i8, v8i16, v4i32, v2i64). When the vector facility is present, we default to the new vector ABI. This is characterized by two major differences: - Vector types are passed/returned in vector registers (except for unnamed arguments of a variable-argument list function). - Vector types are at most 8-byte aligned. The reason for the choice of 8-byte vector alignment is that the hardware is able to efficiently load vectors at 8-byte alignment, and the ABI only guarantees 8-byte alignment of the stack pointer, so requiring any higher alignment for vectors would require dynamic stack re-alignment code. However, for compatibility with old code that may use vector types, when *not* using the vector facility, the old alignment rules (vector types are naturally aligned) remain in use. These alignment rules are not only implemented at the C language level (implemented in clang), but also at the LLVM IR level. This is done by selecting a different DataLayout string depending on whether the vector ABI is in effect or not. Based on a patch by Richard Sandiford. llvm-svn: 236521
2015-05-06 03:25:42 +08:00
; Test v4i32 minimum.
;
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z13 | FileCheck %s
; Test with slt.
define <4 x i32> @f1(<4 x i32> %val1, <4 x i32> %val2) {
; CHECK-LABEL: f1:
; CHECK: vmnf %v24, {{%v24, %v26|%v26, %v24}}
; CHECK: br %r14
%cmp = icmp slt <4 x i32> %val2, %val1
%ret = select <4 x i1> %cmp, <4 x i32> %val2, <4 x i32> %val1
ret <4 x i32> %ret
}
; Test with sle.
define <4 x i32> @f2(<4 x i32> %val1, <4 x i32> %val2) {
; CHECK-LABEL: f2:
; CHECK: vmnf %v24, {{%v24, %v26|%v26, %v24}}
; CHECK: br %r14
%cmp = icmp sle <4 x i32> %val2, %val1
%ret = select <4 x i1> %cmp, <4 x i32> %val2, <4 x i32> %val1
ret <4 x i32> %ret
}
; Test with sgt.
define <4 x i32> @f3(<4 x i32> %val1, <4 x i32> %val2) {
; CHECK-LABEL: f3:
; CHECK: vmnf %v24, {{%v24, %v26|%v26, %v24}}
; CHECK: br %r14
%cmp = icmp sgt <4 x i32> %val2, %val1
%ret = select <4 x i1> %cmp, <4 x i32> %val1, <4 x i32> %val2
ret <4 x i32> %ret
}
; Test with sge.
define <4 x i32> @f4(<4 x i32> %val1, <4 x i32> %val2) {
; CHECK-LABEL: f4:
; CHECK: vmnf %v24, {{%v24, %v26|%v26, %v24}}
; CHECK: br %r14
%cmp = icmp sge <4 x i32> %val2, %val1
%ret = select <4 x i1> %cmp, <4 x i32> %val1, <4 x i32> %val2
ret <4 x i32> %ret
}
; Test with ult.
define <4 x i32> @f5(<4 x i32> %val1, <4 x i32> %val2) {
; CHECK-LABEL: f5:
; CHECK: vmnlf %v24, {{%v24, %v26|%v26, %v24}}
; CHECK: br %r14
%cmp = icmp ult <4 x i32> %val2, %val1
%ret = select <4 x i1> %cmp, <4 x i32> %val2, <4 x i32> %val1
ret <4 x i32> %ret
}
; Test with ule.
define <4 x i32> @f6(<4 x i32> %val1, <4 x i32> %val2) {
; CHECK-LABEL: f6:
; CHECK: vmnlf %v24, {{%v24, %v26|%v26, %v24}}
; CHECK: br %r14
%cmp = icmp ule <4 x i32> %val2, %val1
%ret = select <4 x i1> %cmp, <4 x i32> %val2, <4 x i32> %val1
ret <4 x i32> %ret
}
; Test with ugt.
define <4 x i32> @f7(<4 x i32> %val1, <4 x i32> %val2) {
; CHECK-LABEL: f7:
; CHECK: vmnlf %v24, {{%v24, %v26|%v26, %v24}}
; CHECK: br %r14
%cmp = icmp ugt <4 x i32> %val2, %val1
%ret = select <4 x i1> %cmp, <4 x i32> %val1, <4 x i32> %val2
ret <4 x i32> %ret
}
; Test with uge.
define <4 x i32> @f8(<4 x i32> %val1, <4 x i32> %val2) {
; CHECK-LABEL: f8:
; CHECK: vmnlf %v24, {{%v24, %v26|%v26, %v24}}
; CHECK: br %r14
%cmp = icmp uge <4 x i32> %val2, %val1
%ret = select <4 x i1> %cmp, <4 x i32> %val1, <4 x i32> %val2
ret <4 x i32> %ret
}