2013-05-07 00:17:29 +08:00
|
|
|
; Test floating-point absolute.
|
|
|
|
;
|
|
|
|
; RUN: llc < %s -mtriple=s390x-linux-gnu | FileCheck %s
|
|
|
|
|
|
|
|
; Test f32.
|
|
|
|
declare float @llvm.fabs.f32(float %f)
|
|
|
|
define float @f1(float %f) {
|
2013-07-14 14:24:09 +08:00
|
|
|
; CHECK-LABEL: f1:
|
2013-05-07 00:17:29 +08:00
|
|
|
; CHECK: lpebr %f0, %f0
|
|
|
|
; CHECK: br %r14
|
|
|
|
%res = call float @llvm.fabs.f32(float %f)
|
|
|
|
ret float %res
|
|
|
|
}
|
|
|
|
|
|
|
|
; Test f64.
|
|
|
|
declare double @llvm.fabs.f64(double %f)
|
|
|
|
define double @f2(double %f) {
|
2013-07-14 14:24:09 +08:00
|
|
|
; CHECK-LABEL: f2:
|
2013-05-07 00:17:29 +08:00
|
|
|
; CHECK: lpdbr %f0, %f0
|
|
|
|
; CHECK: br %r14
|
|
|
|
%res = call double @llvm.fabs.f64(double %f)
|
|
|
|
ret double %res
|
|
|
|
}
|
|
|
|
|
|
|
|
; Test f128. With the loads and stores, a pure absolute would probably
|
|
|
|
; be better implemented using an NI on the upper byte. Do some extra
|
|
|
|
; processing so that using FPRs is unequivocally better.
|
|
|
|
declare fp128 @llvm.fabs.f128(fp128 %f)
|
|
|
|
define void @f3(fp128 *%ptr, fp128 *%ptr2) {
|
2013-07-14 14:24:09 +08:00
|
|
|
; CHECK-LABEL: f3:
|
2013-05-07 00:17:29 +08:00
|
|
|
; CHECK: lpxbr
|
|
|
|
; CHECK: dxbr
|
|
|
|
; CHECK: br %r14
|
|
|
|
%orig = load fp128 *%ptr
|
|
|
|
%abs = call fp128 @llvm.fabs.f128(fp128 %orig)
|
|
|
|
%op2 = load fp128 *%ptr2
|
|
|
|
%res = fdiv fp128 %abs, %op2
|
|
|
|
store fp128 %res, fp128 *%ptr
|
|
|
|
ret void
|
|
|
|
}
|