[LLVMdev] New JIT APIs

[Lang Hames]

Just a heads up: The patch is now up for review on llvm-commits. If you
have comments related to the patch please post them in that thread.

Cheers,
Lang.


On Mon, Jan 19, 2015 at 8:43 PM, Lang Hames <lhames at gmail.com> wrote:

> Hi Chuck,
>
>
> > We're currently using LLVM 3.3 in production (due to performance
> regressions in newer versions), so I don't know if > some other scheme is
> appropriate for current levels.
>
> Do you have any insight into what regressed? If it's related to the JIT
> infrastructure I'd be curious to hear about that so I can keep it in mind
> while working on these new APIs. Slowdowns in IR/CodeGen are also
> interesting, though I'm less likely to be able to deal with them personally.
>
> Cheers,
> Lang.
>
>
> On Sun, Jan 18, 2015 at 7:12 AM, Caldarale, Charles R <
> Chuck.Caldarale at unisys.com> wrote:
>
>> > From: Armin Steinhoff [mailto:armin at steinhoff.de]
>> > Subject: Re: [LLVMdev] New JIT APIs
>>
>> > is
>> >  delete EE;   // execution engine
>> >  llvm_shutdown();
>> > sufficient ?
>>
>> AFAICT, llvm_shutdown() must not be called unless you reach a point where
>> LLVM will not be used again by the process (e.g., termination), as it
>> destroys statically allocated objects.  We delete the ExecutionEngine
>> (which automatically deletes TargetMachine and Module) after each
>> compilation.  The LLVMContext and IRBuilder objects are deleted after some
>> configurable number of compilations, in order to avoid unbounded growth in
>> the constant pool.
>>
>> We're currently using LLVM 3.3 in production (due to performance
>> regressions in newer versions), so I don't know if some other scheme is
>> appropriate for current levels.
>>
>>  - Chuck
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150119/917d2ada/attachment.html>