<div dir="ltr">Same here, in fact I'd imagine #6 is the case for many DSLs.<div><br></div><div>v/r,</div><div>Josh</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 4:24 PM, Bill Kelly <span dir="ltr"><<a href="mailto:billk@cts.com" target="_blank">billk@cts.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Greetings,<br>
<div class="im"><br>
Larry Gritz wrote:<br>
> Another usage case, slightly different than your #1:<br>
><br>
> 6. Dynamic code generation (not interactive with respect to the source code)<br>
> - app generates code IR which is compiled as needed for execution<br>
> (important difference: no waiting for a typing human in the loop,<br>
> so very different expectations about responsiveness and bottlenecks)<br>
> - compilation speed IS critical (because many such compilations may be<br>
> necessary and the app itself may be interactive, even if the source code<br>
> entry is not)<br>
> - retained memory use is critical -- ok to use much mem while JITing, but once<br>
> we've reduced it to callable machine code function, we want to reclaim<br>
> as much as possible of the memory needed by LLVM.<br>
> - app is multithreaded and does not want to lock on a single MCJIT --<br>
> ok to have multiple MCJIT's, one per app thread, needing to run<br>
> simultaneously.<br>
<br>
</div>For what it's worth, the above describes my usage case as well. (With the<br>
exception that at present the app uses only a single JIT thread.)<br>
<br>
<br>
Regards,<br>
<br>
Bill<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
</div></div></blockquote></div><br></div></div>