blob: bf0870a86702c4fdeb6dd61f5e77a8b794121597 [file] [log] [blame]
; Test floating-point absolute.
;
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z10 | FileCheck %s
; RUN: llc < %s -mtriple=s390x-linux-gnu -mcpu=z13 | FileCheck %s
; Test f32.
declare float @llvm.fabs.f32(float %f)
define float @f1(float %f) {
; CHECK-LABEL: f1:
; CHECK: lpdfr %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) {
; CHECK-LABEL: f2:
; CHECK: lpdfr %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(ptr %ptr, ptr %ptr2) {
; CHECK-LABEL: f3:
; CHECK: lpxbr
; CHECK: dxbr
; CHECK: br %r14
%orig = load fp128, ptr %ptr
%abs = call fp128 @llvm.fabs.f128(fp128 %orig)
%op2 = load fp128, ptr %ptr2
%res = fdiv fp128 %abs, %op2
store fp128 %res, ptr %ptr
ret void
}