search for: typeresolv

> Nope, types are immutable once created. The only thing you can do is "refine" opaque types to other types. There is a section in the programmer's manual on this: > http://llvm.org/docs/ProgrammersManual.html#TypeResolve > > -Chris So I succeeded in using a "PATypeHolder" for the "opaque" type, define a Type* with PointerType::getUnqual, prepare a field, then use " refineAbstractTypeTo " to built the real type with this added field. The thing is that I would need to do tha...

Hi, We build a type with StructType::get(fModule->getContext(), fDspFields, false); with a fDspFields (std::vector<const llvm::Type*> fDspFields;) that is not yet completely known when we have to build the type. It is possible to add fields in a already build type? Thanks Stéphane Letz

...ve to build the type. It is possible to add fields in a already build type? Nope, types are immutable once created. The only thing you can do is "refine" opaque types to other types. There is a section in the programmer's manual on this: http://llvm.org/docs/ProgrammersManual.html#TypeResolve -Chris

On Jun 15, 2010, at 11:51 AM, Stéphane Letz wrote: >> Nope, types are immutable once created. The only thing you can do is "refine" opaque types to other types. There is a section in the programmer's manual on this: >> http://llvm.org/docs/ProgrammersManual.html#TypeResolve >> >> -Chris > > > So I succeeded in using a "PATypeHolder" for the "opaque" type, define a Type* with PointerType::getUnqual, prepare a field, then use " refineAbstractTypeTo " to built the real type with this added field. > > The thi...

Perhaps somebody out there knows where this link should point: http://llvm.org/docs/ProgrammersManual.html#TypeResolve It simply goes to the top of the document, probably because something has been deleted or the document has been converted to reST. It is found on the last page of the Kaleidoscope tutorial: http://llvm.org/docs/tutorial/LangImpl8.html. -- Mikael -------------- next part -------------- An HTML...

I'd like to be able to make use of a structure type and its fields before it is completely defined. To be specific, let me ask detailed questions at various stages in the construction of a recursive type. I copy from http://llvm.org/docs/ProgrammersManual.html#TypeResolve // Create the initial outer struct PATypeHolder StructTy = OpaqueType::get(); Is it possible to declare variables of type StructTy at this point? Is it possible to define other structured types that have fields of type StructTy at this point? I'm guessing the answers to these quest...

...wrote: > I'd like to be able to make use of a structure type and its fields before > it is completely defined. To be specific, let me ask detailed questions > at various stages in the construction of a recursive type. I copy from > > http://llvm.org/docs/ProgrammersManual.html#TypeResolve > > // Create the initial outer struct > PATypeHolder StructTy = OpaqueType::get(); > > Is it possible to declare variables of type StructTy at this point? I think you can, although you have to be careful; if you don't make sure the variable eventually has a computable si...

I am somewhat confused about how I should go about releasing LLVM types. Some types are owned by a Module, and others I am not sure about. Are there any general rules or guidelines that I should be aware of? It appears to me that whenever I am passing a "new" object into a container type like a module or basic block that the container owns the object. Is that accurate? If this is

I'm working on a personal project which involves lowering a superset of LLVM to "vanilla" LLVM. Part of this involves rewriting types. I'm working off of the 2.6 code base, so this may have been addressed in a bug fix. I'm having trouble with refineAbstractType and recursive types. Specifically, I'm creating opaque types to serve as placeholders for the final

...n 15, 2010, at 11:51 AM, Stéphane Letz wrote: > >>> Nope, types are immutable once created. The only thing you can do is "refine" opaque types to other types. There is a section in the programmer's manual on this: >>> http://llvm.org/docs/ProgrammersManual.html#TypeResolve >>> >>> -Chris >> >> >> So I succeeded in using a "PATypeHolder" for the "opaque" type, define a Type* with PointerType::getUnqual, prepare a field, then use " refineAbstractTypeTo " to built the real type with this added field...

...to be able to make use of a structure type and its fields >> before it is completely defined. To be specific, let me ask detailed >> questions at various stages in the construction of a recursive type. I >> copy from >> >> http://llvm.org/docs/ProgrammersManual.html#TypeResolve >> >> // Create the initial outer struct >> PATypeHolder StructTy = OpaqueType::get(); >> >> Is it possible to declare variables of type StructTy at this point? > > I think you can, although you have to be careful; if you don't make sure > the vari...