search for: libcallify

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, RTLIB::ADD_F80, RTLIB::ADD_PPCF128), N, false); assert(Call.getNode()->getOpcode() == ISD::BUILD_PAIR &&...

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

...rand. 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 instead it uses LibCallify instead. Sorry for the mistake, Micah -----Original Message----- From: Duncan Sands [mailto:baldrick at free.fr] Sent: Wednesday, April 08, 2009 12:25 PM To: llvmdev at cs.uiuc.edu Cc: Villmow, Micah Subject: Re: [LLVMdev] LegalizeFloatType:ExpandFloatRes_FADD Hi Micah, > I'm looking at...