[LLVMdev] MCJIT versus getLazyBitcodeModule?

Larry Gritz lg at larrygritz.com
Tue Jan 21 12:52:20 PST 2014

Thanks for the pointers.

Am I correct in assuming that putting the precompiled bitcode into a second module and linking (or using the object caches) would result in ordinary function calls, but would not be able to inline the functions?

	-- lg

On Jan 21, 2014, at 11:55 AM, Kaylor, Andrew <andrew.kaylor at intel.com> wrote:

> I would say that the incompatibility is by design.  Not that anyone specifically wanted the incompatibility, but rather it's a known artifact of the MCJIT design.
> You can find an example of MCJIT's object caching here: http://blog.llvm.org/2013/08/object-caching-with-kaleidoscope.html
> The two blog entries before that may also be of use to you: http://blog.llvm.org/2013_07_01_archive.html
> I don't where you can find an example of the Module linking I described, but I think llvm::Linker is the class to look at.
> -Andy

Larry Gritz
lg at larrygritz.com

More information about the llvm-dev mailing list