<div dir="ltr">Right, but is there any known use case where Orc's flexibility allows something to be done that couldn't be with MCJIT, apart from lazy compilation?</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 30, 2016 at 12:19 AM, Justin Bogner <span dir="ltr"><<a href="mailto:mail@justinbogner.com" target="_blank">mail@justinbogner.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">Russell Wallace via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> writes:<br>
> When writing a JIT compiler using LLVM, as I understand it, you can use two<br>
> alternative APIs, MCJIT and Orc. The latter offers lazy compilation. Would<br>
> it be accurate to say that if you want eager compilation - always compile<br>
> an entire module upfront - you should use MCJIT?<br>
<br>
</div></div>+lang.<br>
<br>
My understanding is that Orc is strictly more flexible than MCJIT. You<br>
can, in fact, exactly implement the MCJIT API using the Orc APIs.<br>
<br>
I think the general advice is that MCJIT's a bit more mature and stable,<br>
but you probably want Orc in new code unless you really need that<br>
maturity.<br>
</blockquote></div><br></div>