search for: expandconstantfp

Make sure you’re running LLVM with assertions enabled. You’ll get more information about what’s going wrong that way. That said, yes, this looks like a bug. Specifically, SelectionDAGLegalize::ExpandConstantFP() assumes that f32 is the smallest floating point constant type it’ll need to handle, and that MVT enum ordering reflects that. while (SVT != MVT::f32) { SVT = (MVT::SimpleValueType)(SVT.getSimpleVT().SimpleTy - 1); ... } That fun...

...++ on Ubuntu Linux 12.10. 2013/6/17 Jim Grosbach <grosbach at apple.com> > Make sure you’re running LLVM with assertions enabled. You’ll get more > information about what’s going wrong that way. > > That said, yes, this looks like a bug. > Specifically, SelectionDAGLegalize::ExpandConstantFP() assumes that f32 is > the smallest floating point constant type it’ll need to handle, and that > MVT enum ordering reflects that. > > while (SVT != MVT::f32) { > > SVT = (MVT::SimpleValueType)(SVT.getSimpleVT().SimpleTy - 1); > ... > } > > That function,...

Hi, if I write the following simple program: target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128" target triple = "x86_64-unknown-linux-gnu" define void @foo () { %1 = alloca half store half 0xH42CC, half* %1 ; 0xH42CC = 3.4 %2 = load half* %1

...gt; 2013/6/17 Jim Grosbach <grosbach at apple.com> > >> Make sure you’re running LLVM with assertions enabled. You’ll get more >> information about what’s going wrong that way. >> >> That said, yes, this looks like a bug. >> Specifically, SelectionDAGLegalize::ExpandConstantFP() assumes that f32 is >> the smallest floating point constant type it’ll need to handle, and that >> MVT enum ordering reflects that. >> >> while (SVT != MVT::f32) { >> >> SVT = (MVT::SimpleValueType)(SVT.getSimpleVT().SimpleTy - 1); >> ... >&g...

...ch <grosbach at apple.com> >> >>> Make sure you’re running LLVM with assertions enabled. You’ll get more >>> information about what’s going wrong that way. >>> >>> That said, yes, this looks like a bug. >>> Specifically, SelectionDAGLegalize::ExpandConstantFP() assumes that f32 is >>> the smallest floating point constant type it’ll need to handle, and that >>> MVT enum ordering reflects that. >>> >>> while (SVT != MVT::f32) { >>> >>> SVT = (MVT::SimpleValueType)(SVT.getSimpleVT().SimpleTy - 1);...

On Wed, May 20, 2009 at 4:55 PM, Dan Gohman <gohman at apple.com> wrote: > Can you explain why you chose the approach of using a new pass? > I pictured removing LegalizeDAG's type legalization code would > mostly consist of finding all the places that use TLI.getTypeAction > and just deleting code for handling its Expand and Promote. Are you > anticipating something more

On May 20, 2009, at 1:34 PM, Eli Friedman wrote: > On Wed, May 20, 2009 at 1:19 PM, Eli Friedman > <eli.friedman at gmail.com> wrote: > >> Per subject, this patch adding an additional pass to handle vector >> >> operations; the idea is that this allows removing the code from >> >> LegalizeDAG that handles illegal types, which should be a significant

...ment vector, convert it to a - // scalar operation. - (void)ScalarizeVectorOp(Op); - } else { - // This is an illegal multiple element vector. - // Split it in half and legalize both parts. - SDValue X, Y; - SplitVectorOp(Op, X, Y); - } - break; - } -} - /// ExpandConstantFP - Expands the ConstantFP node to an integer constant or /// a load from the constant pool. static SDValue ExpandConstantFP(ConstantFPSDNode *CFP, bool UseCP, @@ -866,58 +655,6 @@ return DAG.getMergeValues(Ops, 2, dl); } -/// UnrollVectorOp - We know that the given vector has a legal type, h...