Displaying 3 results from an estimated 3 matches for "libcallifi".
Did you mean:
libcallify
2009 Apr 08
2
[LLVMdev] LegalizeFloatType:ExpandFloatRes_FADD
I'm looking at the Legalize code and in 2.5 the above function is:
void DAGTypeLegalizer::ExpandFloatRes_FADD(SDNode *N, SDValue &Lo,
SDValue &Hi) {
SDValue Call = LibCallify(GetFPLibCall(N->getValueType(0),
RTLIB::ADD_F32, RTLIB::ADD_F64,
2009 Apr 08
0
[LLVMdev] LegalizeFloatType:ExpandFloatRes_FADD
Hi Micah,
> I'm looking at the Legalize code and in 2.5 the above function is:
>...
> It seems to me that it was switched from a binary function expansion to
> a unary function expansion.
I don't understand the question. The new code is supposed to do exactly
the same thing as the old code. Can you please be more explicit about
what you think the problem is.
> Is my
2009 Apr 08
1
[LLVMdev] LegalizeFloatType:ExpandFloatRes_FADD
In the 2.4 code, it explicitly used 2 Operands to the
MakeLibCall function, whereas in 2.5 it only uses 1 Operand.
Other functions like pow, cos, sin, only use 1 Operand as
I would expect since they are unary functions and div/mul
uses two operands as expected.
But after looking more closely at the code, I realized my
Mistake in thinking that MakeLibCall was the same in both
Cases but