[LLVMdev] Saving/restoring executable code from the the JIT?

[Reid Kleckner]

It's not clear how valuable the feature is if users start to do things
like inlining pointers to heap allocated objects with guards as
optimizations.

I could imagine an IR class representing a pointer to an object on the
heap that gets serialized to bitcode as some kind of relocatable
symbol, and then re-resolved at runtime.  If the corresponding symbol
doesn't exist at runtime, the implementation could choose to drop the
particular function on the floor and recompile from source.

Reid

On Sat, Sep 12, 2009 at 1:01 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:
> Hi.
>
> IIRC some time ago there was some discussion about saving the executable
> code produced by the JIT to a file, for loading it at the next
> session. This would require to stream out the executable code before
> externals are resolved and resolve them when the code is loaded.
>
> AFAIK, LLVM does not support this at the moment.
>
> What's the difficulty of implementing this feature, on terms of existing
> infrastructure etc?
>
> --
> Óscar
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>