search for: palistptr

Throwing this C++ code at the online demo: struct S { double d; unsigned u; }; S foo() { return S(); } produces this LLVM C++ API code: (...) PAListPtr func__Z3foov_PAL = 0; { SmallVector<ParamAttrsWithIndex, 4> Attrs; ParamAttrsWithIndex PAWI; PAWI.index = 0; PAWI.attrs = 0 | ParamAttr::NoUnwind; Attrs.push_back(PAWI); PAWI.index = 1; PAWI.attrs = 0 | ParamAttr::StructRet | ParamAttr::NoAlias; Attrs.push_back(PAW...

...ll.setParamAttrs( > > + Call.getParamAttrs().addAttr(index, > > + ParamAttr::constructAlignmentFromInt(align))); > > +} > > + > > If I call this twice with different values, don't I get the bitwise OR > of the two constructAlignmentFromInt values? Does PAListPtr provide a > better API for this? You are not allowed to set alignment twice - tried it, and got myself an assert. (Is this expected behavior?) > > Thanks Anders! > > — Gordon > > > _______________________________________________ > LLVM Developers mailing list > LLVM...

...TOT are for 2.4. -Tanya On Oct 17, 2008, at 10:52 PM, Óscar Fuentes wrote: > Throwing this C++ code at the online demo: > > struct S { > double d; > unsigned u; > }; > > S foo() { > return S(); > } > > produces this LLVM C++ API code: > > (...) > PAListPtr func__Z3foov_PAL = 0; > { > SmallVector<ParamAttrsWithIndex, 4> Attrs; > ParamAttrsWithIndex PAWI; > PAWI.index = 0; PAWI.attrs = 0 | ParamAttr::NoUnwind; > Attrs.push_back(PAWI); > PAWI.index = 1; PAWI.attrs = 0 | ParamAttr::StructRet | > ParamAttr::N...

...Attrs( >>> + Call.getParamAttrs().addAttr(index, >>> + ParamAttr::constructAlignmentFromInt(align))); >>> +} >> >> If I call this twice with different values, don't I get the bitwise >> OR of the two constructAlignmentFromInt values? Does PAListPtr >> provide a better API for this? > > You are not allowed to set alignment twice - tried it, and got > myself an assert. (Is this expected behavior?) Classy! — Gordon

...truction>(Instr)); > + Call.setParamAttrs( > + Call.getParamAttrs().addAttr(index, > + ParamAttr::constructAlignmentFromInt(align))); > +} > + If I call this twice with different values, don't I get the bitwise OR of the two constructAlignmentFromInt values? Does PAListPtr provide a better API for this? Thanks Anders! — Gordon

Hi Gordon, Thanks a lot for the feedback. I can see I've been way to concentrated on how llvm is build, then on this particular patch. I've done the changes you have suggested and it's now a lot nicer and cleaner! Please do say, if there is anything else. Anders Johnsen On Saturday 26 April 2008 22:02:45 Gordon Henriksen wrote: > Hi Anders, > > Thanks for the patch.

...Call.getParamAttrs().addAttr(index, > >>> + ParamAttr::constructAlignmentFromInt(align))); > >>> +} > >> > >> If I call this twice with different values, don't I get the bitwise > >> OR of the two constructAlignmentFromInt values? Does PAListPtr > >> provide a better API for this? > > > > You are not allowed to set alignment twice - tried it, and got > > myself an assert. (Is this expected behavior?) > > Classy! > > — Gordon > > > _______________________________________________ > LLVM Deve...

...c base class of StringAttributeImpl, EnumAttributeImpl, and IntAttributeImpl. Enums have the attribute kind, integers have a uint64_t value, and strings have two StringRefs for the kind and value. AttributeSet doesn't seem like a good name to me. In the past it was called AttrListPtr and PAListPtr. Today's AttributeSetImpl was called "ParameterAttributeList", which is why we have "PAL" local variables. I'd like to rename AttributeSet to just "AttributeList". It's a list of sets of attributes that is parallel to some function prototype. I already ha...

I'm now writing a pass and I wanna ask a question about how to duplicate the function and add duplicated arguments in llvm, for example: func(int a, char *b) -> func(int a, char *b, int a1, char *b1) I'm now stuck at using "getOrInsertFunction" and how to handle "getArgumentList", please share your opinion, thanks a lot! James