Files
clang-p2996/llvm/test/CodeGen/WebAssembly/libcalls.ll
Bjorn Pettersson 4c7f820b2b Update @llvm.powi to handle different int sizes for the exponent
This can be seen as a follow up to commit 0ee439b705,
that changed the second argument of __powidf2, __powisf2 and
__powitf2 in compiler-rt from si_int to int. That was to align with
how those runtimes are defined in libgcc.
One thing that seem to have been missing in that patch was to make
sure that the rest of LLVM also handle that the argument now depends
on the size of int (not using the si_int machine mode for 32-bit).
When using __builtin_powi for a target with 16-bit int clang crashed.
And when emitting libcalls to those rtlib functions, typically when
lowering @llvm.powi), the backend would always prepare the exponent
argument as an i32 which caused miscompiles when the rtlib was
compiled with 16-bit int.

The solution used here is to use an overloaded type for the second
argument in @llvm.powi. This way clang can use the "correct" type
when lowering __builtin_powi, and then later when emitting the libcall
it is assumed that the type used in @llvm.powi matches the rtlib
function.

One thing that needed some extra attention was that when vectorizing
calls several passes did not support that several arguments could
be overloaded in the intrinsics. This patch allows overload of a
scalar operand by adding hasVectorInstrinsicOverloadedScalarOpd, with
an entry for powi.

Differential Revision: https://reviews.llvm.org/D99439
2021-06-17 09:38:28 +02:00

129 lines
3.7 KiB
LLVM

; RUN: llc < %s -asm-verbose=false -disable-wasm-fallthrough-return-opt -wasm-keep-registers | FileCheck %s
; Test a subset of compiler-rt/libm libcalls expected to be emitted by the wasm backend
target datalayout = "e-m:e-p:32:32-i64:64-n32:64-S128"
target triple = "wasm32-unknown-unknown"
declare fp128 @llvm.sqrt.f128(fp128)
declare fp128 @llvm.floor.f128(fp128)
declare fp128 @llvm.trunc.f128(fp128)
declare fp128 @llvm.nearbyint.f128(fp128)
declare fp128 @llvm.pow.f128(fp128, fp128)
declare fp128 @llvm.powi.f128.i32(fp128, i32)
declare double @llvm.cos.f64(double)
declare double @llvm.log10.f64(double)
declare double @llvm.pow.f64(double, double)
declare double @llvm.powi.f64.i32(double, i32)
declare double @llvm.log.f64(double)
declare double @llvm.exp.f64(double)
declare i32 @llvm.lround(double)
; CHECK-LABEL: fp128libcalls:
define fp128 @fp128libcalls(fp128 %x, fp128 %y, i32 %z) {
; compiler-rt call
; CHECK: call __addtf3
%a = fadd fp128 %x, %y
; CHECK: call __multf3
%b = fmul fp128 %a, %y
; CHECK: call __divtf3
%c = fdiv fp128 %b, %y
; libm calls
; CHECK: call sqrtl
%d = call fp128 @llvm.sqrt.f128(fp128 %c)
; CHECK: call floorl
%e = call fp128 @llvm.floor.f128(fp128 %d)
; CHECK: call powl
%f = call fp128 @llvm.pow.f128(fp128 %e, fp128 %y)
; CHECK: call __powitf2
%g = call fp128 @llvm.powi.f128.i32(fp128 %f, i32 %z)
; CHECK: call truncl
%h = call fp128 @llvm.trunc.f128(fp128 %g)
; CHECK: call nearbyintl
%i = call fp128 @llvm.nearbyint.f128(fp128 %h)
ret fp128 %i
}
; CHECK-LABEL: i128libcalls:
define i128 @i128libcalls(i128 %x, i128 %y) {
; Basic ops should be expanded
; CHECK_NOT: call
%a = add i128 %x, %y
; CHECK: call __multi3
%b = mul i128 %a, %y
; CHECK: call __umodti3
%c = urem i128 %b, %y
ret i128 %c
}
; CHECK-LABEL: f64libcalls:
define i32 @f64libcalls(double %x, double %y, i32 %z) {
; CHECK: call $push{{[0-9]}}=, cos
%a = call double @llvm.cos.f64(double %x)
; CHECK: call $push{{[0-9]}}=, log10
%b = call double @llvm.log10.f64(double %a)
; CHECK: call $push{{[0-9]}}=, pow
%c = call double @llvm.pow.f64(double %b, double %y)
; CHECK: call $push{{[0-9]}}=, __powidf2
%d = call double @llvm.powi.f64.i32(double %c, i32 %z)
; CHECK: call $push{{[0-9]}}=, log
%e = call double @llvm.log.f64(double %d)
; CHECK: call $push{{[0-9]}}=, exp
%f = call double @llvm.exp.f64(double %e)
; CHECK: call $push{{[0-9]}}=, cbrt
%g = call fast double @llvm.pow.f64(double %f, double 0x3FD5555555555555)
; CHECK: call $push{{[0-9]}}=, lround
%h = call i32 @llvm.lround(double %g)
ret i32 %h
}
; fcmp ord and unord (RTLIB::O_F32 / RTLIB::UO_F32 etc) are a special case (see
; comment in WebAssemblyRunimeLibcallSignatures.cpp) so check them separately.
; no libcalls are needed for f32 and f64
; CHECK-LABEL: unordd:
define i1 @unordd(double %x, double %y) {
; CHECK-NOT: call
; CHECK: f64.ne
%a = fcmp uno double %x, %y
; CHECK-NOT: call
; CHECK: f64.eq
%b = fcmp ord double %x, %y
; CHECK: i32.xor
%c = xor i1 %a, %b
ret i1 %c
}
; CHECK-LABEL: unordf:
define i1 @unordf(float %x, float %y) {
; CHECK-NOT: call
; CHECK: f32.ne
%a = fcmp uno float %x, %y
; CHECK-NOT: call
; CHECK: f32.eq
%b = fcmp ord float %x, %y
; CHECK: i32.xor
%c = xor i1 %a, %b
ret i1 %c
}
; CHECK-LABEL: unordt:
define i1 @unordt(fp128 %x, fp128 %y) {
; CHECK: call $push[[CALL:[0-9]]]=, __unordtf2
; CHECK-NEXT: i32.const $push[[ZERO:[0-9]+]]=, 0
; CHECK-NEXT: i32.ne $push{{[0-9]}}=, $pop[[CALL]], $pop[[ZERO]]
%a = fcmp uno fp128 %x, %y
ret i1 %a
}
; CHECK-LABEL: ordt:
define i1 @ordt(fp128 %x, fp128 %y) {
; CHECK: call $push[[CALL:[0-9]]]=, __unordtf2
; CHECK-NEXT: i32.eqz $push{{[0-9]}}=, $pop[[CALL]]
%a = fcmp ord fp128 %x, %y
ret i1 %a
}