Displaying 4 results from an estimated 4 matches for "llvmisdeclaration".
2010 Feb 03
3
[LLVMdev] Interpreter with multiple modules.
...t). If I
try to run the main function, I got the error "LLVM ERROR: Tried to execute
unknown external function: ...".
I build the interpreter giving it M1 and then I add M2. I can use the
LLVMFindFunction(...) to get the functions "funct()" and "main()" and if I
apply LLVMIsDeclaration(...) to these LLVMValueRef, I got false (so the
interpreter should know the two functions are defined and it should be able
to find their code).
Is there something to do to enable the interpreter to find a function in
another module ? I saw there is something like LLVMLinker::LinkModules(...)
in c...
2010 Feb 03
0
[LLVMdev] Interpreter with multiple modules.
...ain function, I got the error "LLVM ERROR: Tried to execute
> unknown external function: ...".
>
> I build the interpreter giving it M1 and then I add M2. I can use the
> LLVMFindFunction(...) to get the functions "funct()" and "main()" and if I
> apply LLVMIsDeclaration(...) to these LLVMValueRef, I got false (so the
> interpreter should know the two functions are defined and it should be able
> to find their code).
>
> Is there something to do to enable the interpreter to find a function in
> another module ? I saw there is something like LLVMLink...
2010 Feb 03
3
[LLVMdev] Interpreter with multiple modules.
...t;LLVM ERROR: Tried to
> execute
> > unknown external function: ...".
> >
> > I build the interpreter giving it M1 and then I add M2. I can use the
> > LLVMFindFunction(...) to get the functions "funct()" and "main()" and if
> I
> > apply LLVMIsDeclaration(...) to these LLVMValueRef, I got false (so the
> > interpreter should know the two functions are defined and it should be
> able
> > to find their code).
> >
> > Is there something to do to enable the interpreter to find a function in
> > another module ? I saw the...
2013 Sep 30
1
[LLVMdev] RFC: llvm-shlib-test (Was: [llvm] r191029 - llvm-c: Make LLVMGetFirstTarget a proper prototype)
Attached is what I got thus far.
What I'm struggling with is proper integration in build system. What
is in there is just wild guesses from my side, both on autoconf and
cmake variants. It would be great if someone with proper knowledge of
the buildsystems could have a look. Also I'm not sure how to properly
handle compilation on msvc - clearly "-std=c11 -Wstrict-prototypes" is