[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
|
|
|
; Verify that we use the vector ABI datalayout if and only if
|
|
|
|
|
; the vector facility is present.
|
|
|
|
|
;
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=generic | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z10 | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z196 | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=zEC12 | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z13 | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-VECTOR %s
|
|
|
|
|
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mattr=vector | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-VECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mattr=+vector | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-VECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mattr=-vector,vector | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-VECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mattr=-vector,+vector | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-VECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mattr=-vector | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mattr=vector,-vector | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mattr=+vector,-vector | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z13 -mattr=-vector | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
|
2020-01-04 07:39:07 +08:00
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z13 -mattr=+soft-float | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z13 \
|
|
|
|
|
; RUN: -mattr=soft-float,-soft-float | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-VECTOR %s
|
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z13 \
|
|
|
|
|
; RUN: -mattr=-soft-float,soft-float | \
|
|
|
|
|
; RUN: FileCheck -check-prefix=CHECK-NOVECTOR %s
|
|
|
|
|
|
[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
|
|
|
%struct.S = type { i8, <2 x i64> }
|
|
|
|
|
|
|
|
|
|
define void @test(%struct.S* %s) nounwind {
|
|
|
|
|
; CHECK-VECTOR-LABEL: @test
|
|
|
|
|
; CHECK-VECTOR: vl %v0, 8(%r2)
|
|
|
|
|
; CHECK-NOVECTOR-LABEL: @test
|
|
|
|
|
; CHECK-NOVECTOR-DAG: agsi 16(%r2), 1
|
|
|
|
|
; CHECK-NOVECTOR-DAG: agsi 24(%r2), 1
|
|
|
|
|
%ptr = getelementptr %struct.S, %struct.S* %s, i64 0, i32 1
|
|
|
|
|
%vec = load <2 x i64>, <2 x i64>* %ptr
|
|
|
|
|
%add = add <2 x i64> %vec, <i64 1, i64 1>
|
|
|
|
|
store <2 x i64> %add, <2 x i64>* %ptr
|
|
|
|
|
ret void
|
|
|
|
|
}
|
|
|
|
|
|