search for: illegaloperation

Duncan: DAGCombine is inserting an IllegalOperation after target-specific instruction legalization has occurred. I'm inserting the fabs and the bitconvert during instruction legalization; DAGCombine is converting the fabs/bitconvert to an 'and' on its second (third?) pass. -scooter On Jan 20, 2009, at 12:24 AM, Duncan Sands wrot...

On Tuesday 20 January 2009 07:52:37 Evan Cheng wrote: > Right. DAGCombine will insert *illegal* nodes before legalize. There are two stages of legalization: legalization of types, followed by legalization of operations. Before type legalization DAGCombine is allowed to create nodes with illegal types and illegal operations. After type legalization but before operation legalization it is

Right. DAGCombine will insert *illegal* nodes before legalize. Evan On Jan 19, 2009, at 8:17 PM, Eli Friedman wrote: > On Mon, Jan 19, 2009 at 6:36 PM, Scott Michel <scottm at aero.org> wrote: >> I just ran across something interesting: DAGCombine inserts a 64-bit >> constant as the result of converting a (bitconvert (fabs val)) to a >> (and (bitconvert val),

...at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Scott Michel > Sent: Tuesday, January 20, 2009 5:53 PM > To: LLVM Developers Mailing List > Subject: Re: [LLVMdev] Shouldn't DAGCombine insert legal nodes? > > Duncan: > > DAGCombine is inserting an IllegalOperation after target-specific > instruction legalization has occurred. I'm inserting the fabs and the > bitconvert during instruction legalization; DAGCombine is converting > the fabs/bitconvert to an 'and' on its second (third?) pass. > > > -scooter > > On Jan 20, 20...