[LLVMdev] [RFC] MCJIT usage models

[Joshua Klontz]

Same here, in fact I'd imagine #6 is the case for many DSLs.

v/r,
Josh


On Mon, Dec 9, 2013 at 4:24 PM, Bill Kelly <billk at cts.com> wrote:

> Greetings,
>
> Larry Gritz wrote:
> > Another usage case, slightly different than your #1:
> >
> > 6. Dynamic code generation (not interactive with respect to the source
> code)
> >    - app generates code IR which is compiled as needed for execution
> >       (important difference: no waiting for a typing human in the loop,
> >        so very different expectations about responsiveness and
> bottlenecks)
> >    - compilation speed IS critical (because many such compilations may be
> >      necessary and the app itself may be interactive, even if the source
> code
> >      entry is not)
> >    - retained memory use is critical -- ok to use much mem while JITing,
> but once
> >      we've reduced it to callable machine code function, we want to
> reclaim
> >      as much as possible of the memory needed by LLVM.
> >    - app is multithreaded and does not want to lock on a single MCJIT --
> >      ok to have multiple MCJIT's, one per app thread, needing to run
> >      simultaneously.
>
> For what it's worth, the above describes my usage case as well.  (With the
> exception that at present the app uses only a single JIT thread.)
>
>
> Regards,
>
> Bill
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131209/2033c5e1/attachment.html>