Displaying 2 results from an estimated 2 matches for "parsedmodule".
2008 Dec 23
2
[LLVMdev] ParseAssemblyString change of behaviour
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 targetM...
2008 Dec 23
0
[LLVMdev] ParseAssemblyString change of behaviour
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.