[LLVMdev] MC-JIT Design
meurant.olivier at gmail.com
Mon Nov 15 14:43:20 CST 2010
2010/11/15 Török Edwin <edwintorok at gmail.com>
> > The pros and cons we discussed:
> > Pro:
> > - We reuse all existing MC output functionality.
> > - We have a shorter path to working well with the external system
> > tools (the real runtime linker, the debugger, the unwinder).
> > Cons:
> > - Requires developing good object file libraries for LLVM. This is
> > also a pro, as it coalesces work other people (Michael Spencer, Nick
> > Kledzik) are already interested in doing.
> > - Means JIT is slightly more platform dependent, as the runtime
> > linker could have ELF or Mach-O specific bugs that wouldn't show up on
> > another platform.
> Don't forget PE (or is it pecoff?), otherwise JIT won't work on win32.
> But what does the obj format has to do with the JIT?
> Sure for debug info its good to have an ELF around to give to gdb, but
> otherwise can't you just emit the code to memory, with a small header
> to keep info you need, and thats it?
If I understand correctly, the idea is to use native platform format (ELF,
Mach-O, COFF...) even when emitting code in memory for the JIT.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the LLVMdev