search for: llvm_get_function_pointer

...(PM, ... ) llvm_run_passes(PM,M); // merge modules - not relevant here // make an execution engine from the module void * JE = llvm_make_jit_engine (M); // get a function pointer by name. If you have several functions with the same // name, you are out of luck int (*fib) (int) = (int (*)(int)) llvm_get_function_pointer(JE,M,"fib"); // the above cast is probably wrong. int result =fib (24); -- -Alex

On Thu, 5 May 2005, Alexander Friedman wrote: >>> Does there happen to be a C interface to the jit ? Our scheme impl >>> has a good FFI, but it doesn't do C++. If not, this is no big deal, >>> and i'll just write something myself. >> >> No, but such bindings would be *very useful*. And since there might be >> other people who need them this

...gt; // merge modules - not relevant here > > // make an execution engine from the module > void * JE = llvm_make_jit_engine (M); > > // get a function pointer by name. If you have several functions with the same > // name, you are out of luck > int (*fib) (int) = (int (*)(int)) llvm_get_function_pointer(JE,M,"fib"); > > // the above cast is probably wrong. > > int result =fib (24); Looks good! -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/

> So as it stands, one should think of out JIT as something akin to the > early Java JITs: one function at a time and only one compile per > function. This is extremely primative by modern JIT standards, where a > JIT will do profiling, find hot functions and reoptimize them, > reoptimize functions when more information about the call tree is > available, have several levels of