search for: selectiondagnodes

FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/io.llx: Assertion failed: (ResNo < Values.size() && "Illegal result number!"), function getValueType, file /usr/home/llvm/obj/../include/llvm/CodeGen/SelectionDAGNodes.h, line 507. Abort trap (core dumped) FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/ioport.llx: Assertion failed: (ResNo < Values.size() && "Illegal result number!"), function getValueType, file /usr/home/llvm/obj/../include/llvm/CodeGen/SelectionDAGNodes.h, line 5...

Folks, I'm tracking down a buildbot failure on our self-hosting bot, and because there are several dozens of commits to track on a self-hosting issue (direct compilation goes well), I thought that showing the error on the list would be faster. src/include/llvm/CodeGen/SelectionDAGNodes.h:625: llvm::EVT llvm::SDNode::getValueType(unsigned int) const: Assertion `ResNo < NumValues && "Illegal result number!"' failed. Git blame around that line pointed me at Chris in 2005 and Owen in 2009, which is obviously not what broke the build. Anyone working on that a...

On Sat, 14 May 2005, Jeff Cohen wrote: > FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/io.llx: > Assertion failed: (ResNo < Values.size() && "Illegal result number!"), > function getValueType, file > /usr/home/llvm/obj/../include/llvm/CodeGen/SelectionDAGNodes.h, line 507. > Abort trap (core dumped) > > FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/ioport.llx: > Assertion failed: (ResNo < Values.size() && "Illegal result number!"), > function getValueType, file > /usr/home/llvm/obj/../include/llvm/CodeGe...

...4 May 2005, Jeff Cohen wrote: > >> FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/io.llx: >> Assertion failed: (ResNo < Values.size() && "Illegal result >> number!"), function getValueType, file >> /usr/home/llvm/obj/../include/llvm/CodeGen/SelectionDAGNodes.h, line >> 507. >> Abort trap (core dumped) >> >> FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/ioport.llx: >> Assertion failed: (ResNo < Values.size() && "Illegal result >> number!"), function getValueType, file >> /usr/ho...

...Sat, 2005-05-14 at 07:16 -0700, Jeff Cohen wrote: > FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/io.llx: > Assertion failed: (ResNo < Values.size() && "Illegal result number!"), > function getValueType, file > /usr/home/llvm/obj/../include/llvm/CodeGen/SelectionDAGNodes.h, line 507. > Abort trap (core dumped) > > FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/ioport.llx: > Assertion failed: (ResNo < Values.size() && "Illegal result number!"), > function getValueType, file > /usr/home/llvm/obj/../include/llvm/CodeG...

...e/ben/svn-work/llvm/include/llvm/Target/TargetLowering.h:26, from /disk1.1/tigris-slash/usr/home/ben/svn-work/llvm/include/llvm/Transforms/Utils/AddrModeMatcher.h:24, from AddrModeMatcher.cpp:14: /disk1.1/tigris-slash/usr/home/ben/svn-work/llvm/include/llvm/CodeGen/SelectionDAGNodes.h:1934: error: base `llvm::SDNode' with only non-default constructor in class without a constructor and, indeed, it appears to be true. Puzzled how this is building for anyone else, and also not really much clue what to do to fix...

...nstruction: store [65536 x i8] zeroinitializer, [65536 x i8]* %buf.i, align 16 ... which causes the SelectionDAG code to assert out: Assertion failed: (ResNo < NumValues && "Illegal result number!"), function getValueType, file /Users/criswell/src/llvm/include/llvm/CodeGen/SelectionDAGNodes.h, line 589. Should LLVM be able to code generate the above store instruction? If not, how large a value can a store instruction store to memory without triggering problems in the code generator? -- John T.

...ecent resources as to what all this stuff actually does? And how to figure out what's going wrong when it inevitably does go wrong? So far all I've found is include/llvm/Target/TargetSelectionDAG.td, which at least lists them but doesn't say what they do, and the C++ implementations in SelectionDAGNodes.h, which is entirely undocumented... -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ │ "You cannot truly appreciate _Atlas Shrugged_ until you have read it │ in the original Klingon." --- Sea Wasp on r.a.sf.w -------------- next part -------------- A non-text attachment was...

...include/llvm/Target/TargetLowering.h:26, > from > /disk1.1/tigris-slash/usr/home/ben/svn-work/llvm/include/llvm/Transforms/Utils/AddrModeMatcher.h:24, > from AddrModeMatcher.cpp:14: > /disk1.1/tigris-slash/usr/home/ben/svn-work/llvm/include/llvm/CodeGen/SelectionDAGNodes.h:1934: > error: base `llvm::SDNode' with only non-default constructor in class > without a constructor > > and, indeed, it appears to be true. Puzzled how this is building for > anyone else, and also not really much clue what to do to fix... > _______________________________...

Hi, The attached patch implements sub.ovf/mul.ovf intrinsics similarly to the recently added add.ovf intrinsics. These are useful for implementing some vm instructions like sub.ovf/mul.ovf in .NET IL efficiently. sub.ovf is supported in target independent lowering and on x86, while mul.ovf is only supported in the x86 backend. Please review

...o go about creating patch files etc, but would like to contribute to the project). Also, I'm using MS Visual C++ Express, and there are a few things that stop llvm1.9 (and the current CVS release) from compiling correctly - once again, not sure how to submit, but here are the main things - In SelectionDAGNodes.h StoreSDNode(SDOperand Chain, SDOperand Value, SDOperand Ptr, SDOperand Off, ISD::MemOpAddrMode AM, bool isTrunc, MVT::ValueType SVT, const Value *SV, int O=0, unsigned Align=0, bool Vol=false) SDOperand Value should really be SDOperand value (lower case), sinc...

Hi, The document for "Adding a new SelectionDAG node" ( @ http://llvm.org/releases/2.9/docs/ExtendingLLVM.html#sdnode ) says, "1. include/llvm/CodeGen/SelectionDAGNodes.h: Add an enum value for the new SelectionDAG node." Where exactly shall one add the info for new SelectionDAG ? I dont see enums for other SDnodes too. Please help. Regards, Ankur

...x i8] zeroinitializer, [65536 x i8]* %buf.i, align 16 > > ... which causes the SelectionDAG code to assert out: > > Assertion failed: (ResNo < NumValues && "Illegal result number!"), > function getValueType, file > /Users/criswell/src/llvm/include/llvm/CodeGen/SelectionDAGNodes.h, line 589. > > Should LLVM be able to code generate the above store instruction?  If > not, how large a value can a store instruction store to memory without > triggering problems in the code generator? I don't know the exact limit, but if you're storing an array or struct wi...

...hin 85 lines of code, none of which have anything to do with its size. Therefore, increasing the size of Ops shouldn't at all affect the behaviour of LLVM, we supposed. Much to our surprise, this isn't as trivial. Even this innocuous change: ==================== --- a/include/llvm/CodeGen/SelectionDAGNodes.h +++ b/include/llvm/CodeGen/SelectionDAGNodes.h @@ -1068,6 +1068,7 @@ public: /// class AtomicSDNode : public MemSDNode { SDUse Ops[4]; + SDUse buffer; void InitAtomic(AtomicOrdering Ordering, SynchronizationScope SynchScope) { // This must match encodeMemSDNodeFlags() in SelectionD...

...e only thing > I can think of is that the IR is treating the Booleans as i1 and therefore > either and'ing or xor'ing the results of my comparison with the value 1. CodeGen assumes that SETCC(true condition) & 1 == 1, and SETCC(false condition) & 1 == 0. For details, look in SelectionDAGNodes.h. If your comparisons are returning something unusual, you may have to custom-lower them. > I have no clue how the 1 gets put in there (!(idx > 0)) == (idx <= 0) == (idx < 1). Most likely the DAGCombiner is doing this. What should be happening is something like the following: Bra...

...65536 x i8]* %buf.i, align 16 >> >> ... which causes the SelectionDAG code to assert out: >> >> Assertion failed: (ResNo< NumValues&& "Illegal result number!"), >> function getValueType, file >> /Users/criswell/src/llvm/include/llvm/CodeGen/SelectionDAGNodes.h, line 589. >> >> Should LLVM be able to code generate the above store instruction? If >> not, how large a value can a store instruction store to memory without >> triggering problems in the code generator? > I don't know the exact limit, but if you're storing a...

...m/include/llvm/Target/TargetLowering.h:26, > from > /disk1.1/tigris-slash/usr/home/ben/svn-work/llvm/include/llvm/Transforms/Utils/AddrModeMatcher.h:24, > from AddrModeMatcher.cpp:14: > /disk1.1/tigris-slash/usr/home/ben/svn-work/llvm/include/llvm/CodeGen/SelectionDAGNodes.h:1934: > error: base `llvm::SDNode' with only non-default constructor in class > without a constructor > > and, indeed, it appears to be true. Puzzled how this is building for > anyone else, and also not really much clue what to do to fix... > ________________________________...

...at an actual target. > > Is my understanding correct? Also, is there any document describing the > selection DAG nodes that one needs to match against? The "how to write a backend" documents are relevant. As are existing targets. The comments on the opcodes in include/CodeGen/SelectionDAGNodes.h are fairly descriptive as well. > And what's the > algorithm behind this selection DAG? The underlying algorithm is a fairly simple bottom-up tiling. > > I'm also wondering what would be the possible improvement of the approach > presented last Friday at POPL > (h...

...th --fast, the blocks stay around, so it must be an optimization pass of some sort that doesn't realize my new instruction is branch-like. How do I tell LLVM to not delete the target blocks of my instruction? Here's a list of files I've modified so far: M llvm-2.3/include/llvm/CodeGen/SelectionDAGNodes.h M llvm-2.3/include/llvm/Instruction.def M llvm-2.3/include/llvm/Instructions.h M llvm-2.3/include/llvm/Support/InstVisitor.h M llvm-2.3/lib/AsmParser/LLLexer.cpp M llvm-2.3/lib/AsmParser/llvmAsmParser.cpp.cvs M llvm-2.3/lib/AsmParser/llvmAsmParser.h.cvs M llvm-2.3/lib/AsmParser/llvmAsmParser.y M...

...ode(ISD::ADD, DAG.getVTList(MVT::Other, MVT::i32), >> &Ops[0], Ops.size()); >> >> Isn't that the way how it is supposed to work? > > ADD does not use a chain, so there's no chain operand, or > MVT::Other result for it in an ADD node. You might want to look at SelectionDAGNodes.h, that has some (informal) description of what operands and results the nodes have.