search for: classllvm_1_1sys_1_1dynamiclibrary

...red library linked into your program. Otherwise you just put the function into a shared library and load that library through llvm::sys::DynamicLibrary::LoadLibraryPermanently() [2]. Then the JIT resolves it without the shared library being linked at compile/link time. [2] http://llvm.org/doxygen/classllvm_1_1sys_1_1DynamicLibrary.html Only in unusual circumstances (i.e., you can't/don't want want to put the stuff into a separate shared library *and* your C compiler doesn't support backlinking a la -rdynamic), it's necessary to explicitly tell the dynamic loader about your C function, by calling sys::Dynamic...

On Jul 2, 2009, at 1:05 AM, Carter Cheng wrote: > I am having some difficulties getting the LLVM JIT to resolve extern > "C" functions which I have defined in source file and invoking them > via EE::runFunction() after generating a Function prototype for it. > Is this possible or do I need to generate a .so for my functions are > link against it? If the JIT needs

Hi, I am having some difficulties getting the LLVM JIT to resolve extern "C" functions which I have defined in source file and invoking them via EE::runFunction() after generating a Function prototype for it. Is this possible or do I need to generate a .so for my functions are link against it? Thanks in advanced, Carter. Sorry for the double post but apparently I mistakenly tagged