search for: settyp

...roblems in defining new generic functions and classes. Just have a look at the following example: require(fPortfolio) setClass("PROBECLASS", representation( type="character" ) ) isGeneric("setType<-") #Returns TRUE #I would like to define a specific function for class PROBECLASS with other arguments than for the generic function "setType" of fPortfolio. setGeneric("setType<-", function(object, value) standardGeneric("setType<-")) #Returns Fehle...

...roblems in defining new generic functions and classes. Just have a look at the following example: require(fPortfolio) setClass("PROBECLASS", representation( type="character" ) ) isGeneric("setType<-") #Returns TRUE #I would like to define a specific function for class PROBECLASS with other arguments than for the generic function "setType" of fPortfolio. setGeneric("setType<-", function(object, value) standardGeneric("setType<-")) #Returns Fehle...

...MED abbrevid=8 op0=0 op1=0 op2=6/> <POINTER abbrevid=4 op0=7 op1=0/> - <STRUCT_ANON abbrevid=6 op0=0 op1=0 op2=6/> </TYPE_BLOCK_ID> <GLOBALVAR abbrevid=4 op0=8 op1=0 op2=2 op3=0 op4=0 op5=0/> <CONSTANTS_BLOCK NumWords=5 BlockCodeSize=4> - <SETTYPE abbrevid=4 op0=9/> + <SETTYPE abbrevid=4 op0=7/> <NULL/> </CONSTANTS_BLOCK> ... all the same ... So it pretty much seems that instantiating a constant struct with a type which is structurally identical to an existing named struct type creates a new anonymous...

Hello. I've managed to create a bitcode file (attached; also available at [1]) which produces a series of identical errors when verified: | Global variable initializer type does not match global variable type! | %i.NilClass* @nil When ran through llvm-dis and recompiled, through, it verifies successfully. If I disassemble it one more time, the result is identical to the first

...res.data.f32 = (float) imm0.reg.data.s16; break; + case TYPE_S32: res.data.f32 = (float) imm0.reg.data.s32; break; + default: + return; + } + i->setSrc(0, bld.mkImm(res.data.f32)); + break; + default: + return; + } + i->setType(i->dType); /* Remove i->sType, which we don't need anymore */ + i->setSrc(1, NULL); + i->op = OP_MOV; + + i->src(0).mod = Modifier(0); /* Clear the already applied modifier */ + break; + } default: return; } -- 2.2.1

...res.data.f32 = (float) imm0.reg.data.s16; break; + case TYPE_S32: res.data.f32 = (float) imm0.reg.data.s32; break; + default: + return; + } + i->setSrc(0, bld.mkImm(res.data.f32)); + break; + default: + return; + } + i->setType(i->dType); /* Remove i->sType, which we don't need anymore */ + i->setSrc(1, NULL); + i->op = OP_MOV; + + i->src(0).mod = Modifier(0); /* Clear the already applied modifier */ + break; + } default: return; } -- 2.2.1

...c/llvm/lib/TableGen/Main.cpp:117 #15 0x00000001002d0864 in main (argc=11, argv=0x7fff5fbff8f8) at /Users/jholewinski/projects/llvm/src/llvm/utils/TableGen/TableGen.cpp:181 The fault occurs in CodeGenDAGPatterns.cpp: 2781 for (unsigned i = 0; i != NumResults; ++i) 2782 ResultPattern->setType(i, Res0Node->getExtType(i)); Res0Node has only 1 type, but it is expected to have 2. Looking at the X86 back-end code, it looks like there do exist multi-output instructions, but they all use physical (implicit) registers for the second destination, not arbitrary register types. And if I ch...

...#15 0x00000001002d0864 in main (argc=11, argv=0x7fff5fbff8f8) at > /Users/jholewinski/projects/llvm/src/llvm/utils/TableGen/TableGen.cpp:181 > > > The fault occurs in CodeGenDAGPatterns.cpp: > > 2781 for (unsigned i = 0; i != NumResults; ++i) > 2782 ResultPattern->setType(i, Res0Node->getExtType(i)); > > Res0Node has only 1 type, but it is expected to have 2. > > > Looking at the X86 back-end code, it looks like there do exist > multi-output instructions, but they all use physical (implicit) registers > for the second destination, not arbitr...

...t; #15 0x00000001002d0864 in main (argc=11, argv=0x7fff5fbff8f8) at /Users/jholewinski/projects/llvm/src/llvm/utils/TableGen/TableGen.cpp:181 > > > The fault occurs in CodeGenDAGPatterns.cpp: > > 2781 for (unsigned i = 0; i != NumResults; ++i) > 2782 ResultPattern->setType(i, Res0Node->getExtType(i)); > > Res0Node has only 1 type, but it is expected to have 2. > > > Looking at the X86 back-end code, it looks like there do exist multi-output instructions, but they all use physical (implicit) registers for the second destination, not arbitrary reg...

...4 in main (argc=11, argv=0x7fff5fbff8f8) at /Users/jholewinski/projects/llvm/src/llvm/utils/TableGen/TableGen.cpp:181 >> >> >> The fault occurs in CodeGenDAGPatterns.cpp: >> >> 2781 for (unsigned i = 0; i != NumResults; ++i) >> 2782 ResultPattern->setType(i, Res0Node->getExtType(i)); >> >> Res0Node has only 1 type, but it is expected to have 2. >> >> >> Looking at the X86 back-end code, it looks like there do exist multi-output instructions, but they all use physical (implicit) registers for the second destinatio...

...data.f64 = (double) imm0.reg.data.s16; break; + case TYPE_S32: res.data.f64 = (double) imm0.reg.data.s32; break; + default: + return; + } + i->setSrc(0, bld.mkImm(res.data.f64)); + break;*/ + default: + return; + } + i->setType(i->dType); /* Remove i->sType, which we don't need anymore */ + i->setSrc(1, NULL); + i->op = OP_MOV; + + i->src(0).mod = Modifier(0); /* Clear the already applied modifier */ + break; + } default: return; } -- 1.8.4.5

...does sound like a useful use-case, but I am uncomfortable with > making DepthFirstIterator any heavier > BTW: in order to make DepthFirstIterator more lightweight wouldn't it be better to make the visit tracking an opt-in. Thus don't provide llvm::SmallPtrSet as a default for SetType but a simple stub class implementing count and insert only. I've never used the visit tracking option so far and it costs a lot in terms of speed and memory. Best Olaf Krzikalla -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: df_iterato...

Would it be possible to replace all uses of the i64 (bitcast Instruction) with bitcast operand? So for something like: tmp = bitcast %struct.MyStruct* %arrayidx to i64* I would like to replace all uses of tmp with arrayidx. It doesn't look like LLVM has a way to setType() so I guess I would have to check uses, and create new instructions of the StructTy and replace those uses with the new Instruction? On Thu, Jun 28, 2012 at 3:27 PM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Thu, Jun 28, 2012 at 3:04 PM, Ryan Taylor <ryta1203 at gmail.com&...

Hi Greg, I'm afraid I've not looked into the infrastructure Jim put into place, so I've not really been able to answer the "how should I do it" questions, but hopefully I can comment on the ABI. > And probably questions for Tim, are these "section-relative" mapping > symbols, as defined in 4.6.5.1 of the ELF for ARM document? Yes, they are. > And what

Hi David, > "LLVM type size doesn't match GCC type size!"' failed. this assertion checks that gcc types are converted into LLVM types of the same size. Try running cc1 in gdb. When you hit the assertion, go up a few stack frames until you get to ConvertType. Do call debug_tree(type) That will tell you what the gcc type was. From that and the LLVM type it should be clear

...res.data.f32 = (float) imm0.reg.data.s16; break; + case TYPE_S32: res.data.f32 = (float) imm0.reg.data.s32; break; + default: + return; + } + i->setSrc(0, bld.mkImm(res.data.f32)); + break; + default: + return; + } + i->setType(i->dType); /* Remove i->sType, which we don't need anymore */ + i->op = OP_MOV; + i->src(0).mod = Modifier(0); /* Clear the already applied modifier */ + break; + } default: return; } -- 2.2.1

...double) imm0.reg.data.s16; break; + case TYPE_S32: res.data.f64 = (double) imm0.reg.data.s32; break; + default: + return; + } + i->setSrc(0, bld.mkImm(NULL, imm0.reg.data.f64)); + break; */ + default: + return; + } + i->setType(i->dType); /* Remove i->sType, which we don't need anymore */ + i->setSrc(1, NULL); + i->op = OP_MOV; + + i->src(0).mod = Modifier(0); /* Clear the already applied modifier */ + break; + } default: return; } -- 1.8.4.5

I attached a rails helper implementation of the fb_table described here: http://wiki.developers.facebook.com/index.php/Facebook_Styles I included testing and comments. I hope you find it useful. Curiously, it''s really a small extension of FBML. Richard -------------- next part -------------- Index: test/rails_integration_test.rb

...be a function pointer of size 32, which would indicate 32-bit code. The llvm type is PointerTyID of size 64, indicating 64-bit code. This happens at line 796 of llvm-types.cpp: if (Ty->getTypeID() == Type::VoidTyID) Ty = Type::Int8Ty; // void* -> sbyte* return TypeDB.setType(type, PointerType::get(Ty)); Somehow PointerType::get is returning a 64-bit pointer even though -m32 was passed to llvm-gcc. I'll see if I can figure out where the 64-bit code warning is emitted and what triggers it. -Dave

...gt; + case TYPE_S32: res.data.f32 = (float) imm0.reg.data.s32; break; > + default: > + return; > + } > + i->setSrc(0, bld.mkImm(res.data.f32)); > + break; > + default: > + return; > + } > + i->setType(i->dType); /* Remove i->sType, which we don't need anymore */ > + i->setSrc(1, NULL); How can src(1) be set? OP_CVT only has the one arg... > + i->op = OP_MOV; > + > + i->src(0).mod = Modifier(0); /* Clear the already applied modifier */ > +...