[LLVMdev] ExecutionEngine always comes back NULL

Rick Mann rmann at latencyzero.com
Wed Jan 9 15:11:04 PST 2013

On Jan 9, 2013, at 9:09 , Óscar Fuentes <ofv at wanadoo.es> wrote:

> I guess that instantiating the JIT on that way would force the clients
> to link with that feature (which exists only on selected platforms.) If
> the user wants the interpreter, why should he be forced to include the
> JIT on the final executable? And vice-versa: if you are interested only
> on the JIT, why should your executable carry the weight of the
> interpreter?

I can think of at least a couple of ways to handle that so that it's explicit: either instantiate a sub-class of ExecutionEngine that uses JIT, or instantiate a JIT explicitly to pass to ExecutionEngine. Or calling ExecutionEngine::createJIT() should cause a link-time error (but not if it's not called).


More information about the llvm-dev mailing list