search for: targetmodul

Hi, when upgrading my compiler from LLVM 2.1 to 2.4 I stumbled upon a change of behaviour in ParseAssemblyString. For an interactive toplevel I am generating .ll source and feeding it into ParseAssemblyString like this: Module* parsedModule = ParseAssemblyString( code, targetModule, &errorInfo ); where targetModule is the module I expect all the LLVM code to go. Until 2.1 the globals, types and functions in code where added to targetModule. Since 2.2 this does not happen anymore. The documentation still states that targetModule is "A module to add the asse...

On Dec 23, 2008, at 7:15 AM, Jan Rehders wrote: > Hi, > > when upgrading my compiler from LLVM 2.1 to 2.4 I stumbled upon a > change of behaviour in ParseAssemblyString. For an interactive > toplevel I am generating .ll source and feeding it into > ParseAssemblyString like this: Hi Jan, I don't think that there is any intentional change here. It sounds like a bug.

...ctured to allow after declaration global or local structured variables. How I can I do? Thanks, Manuele Il 31/01/2013 10:14, Garba,Peter ha scritto: > Hi, > > that's what I'm doing ... > > //Init the struct type > llvm::StructType *structReg = llvm::StructType::create(TargetModule->getContext(),vMember, "struct.Foo"); > structRegPtr = llvm::PointerType::get(structReg, 0); > > //Create a llvm function > llvm::FunctionType* ty = llvm::FunctionType::get(llvm::Type::getInt32Ty(TargetModule->getContext()),structRegPtr,false); > llvm::C...

Hi All, I tryed to create a global structured derived declaration in my compiler by: StructType *st = StructType(getGlobalContext(), elements, false); In dump module i didn't find any code needed to declare a new user data type. Is there a instruction to add this class into current module? Cheers, Manuele