[LLVMdev] MCJIT versus getLazyBitcodeModule?
lg at larrygritz.com
Mon Jan 20 11:28:44 PST 2014
I'm having a problem with MCJIT (in LLVM 3.3 and 3.4), in which it's not resolving symbol mangling in a precompiled bitcode in the same way as old JIT. It's possible that it's just my misunderstanding. Maybe somebody can spot my problem, or identify it as an MCJIT bug.
Here's my situation, in a nutshell:
* I am assembling IR and JITing in my app. The IR may potentially make calls to a large body of code that I precompile to bitcode using "clang++ -S --emit-llvm", then create a .cpp file containing the bitcode, which is compiled into my app.
* Before JITing the dynamic code, my app initializes the Module like this:
llvm::MemoryBuffer* buf =
llvm::MemoryBuffer::getMemBuffer (llvm::StringRef(bitcode, bitcode_size), name);
llvm::Module *m = llvm::getLazyBitcodeModule (buf, context(), err);
where bitcode is a big char array holding the precompiled bitcode. The idea is to
"seed" the module with that precompiled bitcode so that any calls I inserted into the IR
will work properly.
* When I JIT, I just refer to functions in the bitcode like "foo", if that's what I called it in the original .cpp file that was turned into bitcode.
* Traditionally, I have created a JIT execution engine like this:
m_llvm_exec = llvm::ExecutionEngine::createJIT (module(), err,
All has worked fine, this is a system that's seen heavy production use for a couple years now.
Now I'm trying to make this codebase work with MCJIT, and I've run into some trouble. Here's how I'm setting up the ExecutionEngine for the MCJIT case:
m_llvm_exec = llvm::EngineBuilder(module())
USE_MCJIT is 1 when I'm building the code to use MCJIT. I'm initializing the buffer and seeding it with the precompiled bitcode in the same way as always, as outlined above.
The basic problem is that it's not finding the symbols in that bitcode.. I get an error message back like this:
Program used external function '_foo' which could not be resolved!
So it seems that it's an issue of whether or not the underscore prefix is included when looking up the function from the module, and old JIT and MCJIT disagree.
Furthermore, if I change the creation of the module from using llvm::getLazyBitcodeModule to this:
llvm::Module *m = llvm::ParseBitcodeFile (buf, context(), err);
it works just fine. But of course, I'd really like to deserialize this bitcode file lazily, because it's got a ton of functions potentially called by my IR, but any given bit of code that I'm JITing only uses a tiny subset, so the JIT speed has greatly reduced overhead (10-20x!) when using the lazy option, so that's considered fairly critical for our app.
So, in short:
old JIT + ParseBitcodeFile = works
old JIT + getLazyBitcodeModule = works
MCJIT + ParseBitcodeFile = works
MCJIT + getLazyBitcodeModule = BROKEN
Does anybody have advice? Thanks in advance for any help.
lg at larrygritz.com
More information about the llvm-dev