5fb2797f23
The current values for PrivateGlobalPrefix and PrivateLabelPrefix (@@ and @ respectively) are, in hindsight, poor choices for multiple reasons: First, there exist externally visible routines from the language environment that begin with @@. These functions are certainly not local/private by any means and they should not share a prefix with private globals. Secondly, both private globals and private labels should be handled the same way by GOFF, so it doesn't make much sense for them to have separate prefixes. GOFF remains the only file format where these are different and there is no reason for that to be the case
32 lines
796 B
LLVM
32 lines
796 B
LLVM
; Test the passing of scalar i128 values on z/OS.
|
|
;
|
|
; RUN: llc < %s -mtriple=s390x-ibm-zos -mcpu=z13 | FileCheck %s
|
|
|
|
; CHECK-LABEL: call_i128:
|
|
; CHECK-DAG: larl 1, L#CPI0_0
|
|
; CHECK-DAG: vl 0, 0(1), 3
|
|
; CHECK-DAG: vst 0, 2256(4), 3
|
|
; CHECK-DAG: larl 1, L#CPI0_1
|
|
; CHECK-DAG: vl 0, 0(1), 3
|
|
; CHECK-DAG: vst 0, 2272(4), 3
|
|
; CHECK-DAG: la 1, 2288(4)
|
|
; CHECK-DAG: la 2, 2272(4)
|
|
; CHECK-DAG: la 3, 2256(4)
|
|
|
|
define i128 @call_i128() {
|
|
entry:
|
|
%retval = call i128 (i128, i128) @pass_i128(i128 64, i128 65)
|
|
ret i128 %retval
|
|
}
|
|
|
|
; CHECK-LABEL: pass_i128:
|
|
; CHECK: vl 0, 0(3), 3
|
|
; CHECK: vl 1, 0(2), 3
|
|
; CHECK: vaq 0, 1, 0
|
|
; CHECK: vst 0, 0(1), 3
|
|
define i128 @pass_i128(i128 %arg0, i128 %arg1) {
|
|
entry:
|
|
%N = add i128 %arg0, %arg1
|
|
ret i128 %N
|
|
}
|