Displaying 3 results from an estimated 3 matches for "llvm_jit_compil".
Did you mean:
llvm_jit_compile
2009 Feb 12
0
[LLVMdev] fastcc, tail calls, and gcc
Jeff Kuskin wrote:
> Correct? If not, how do I call a LLVM JIT-generated fastcc function
> from a function statically compiled by GCC?
Well, you can always generate a little wrapper function with C calling
convention which just calls the fastcc function.
--
Dr. Albert Gr"af
Dept. of Music-Informatics, University of Mainz, Germany
Email: Dr.Graef at t-online.de, ag at
2009 Feb 13
1
[LLVMdev] fastcc, tail calls, and gcc
...compiled by GCC?
>
> Well, you can always generate a little wrapper function with C calling
> convention which just calls the fastcc function.
>
I use the fastcall convention all the time.
LLVM-jitted code calling GCC-compile code and vice-versa.
This works for x86 (32 bit):
void* llvm_jit_compile();
typedef __attribute__((fastcall)) int (*func_ptr)(int p1, int p2);
int g(void) {
func_ptr f = (func_ptr)llvm_jit_compile();
return f(1, 2);
}
Mark
2009 Feb 12
6
[LLVMdev] fastcc, tail calls, and gcc
Two related questions.
This is with LLVM 2.4 doing a JIT compile to x86-64. (I generate LLVM
IR using an IRBuilder instance, compile/optimize, and then call
getPointerToFunction() to get a "native" function pointer.)
(1) My reading of various mailing list messages seems to indicate
that a function marked as using the "fastcc" calling convention