Thank you all very much!
Of course I don't want to present trace-based JITs as the best choice, but leave some hints on the "possible"
advantages that it "possibly" offers, just to put an additional comment on my graphs.
So it has come down to this:
Trace-based JIT compilation allows more specialized optimizations on code and is potentially
more well suited for modern CPUs \cite{PyPy,Dynamo}
...
here we also see the possible advantages of tracing JIT since ... scalable ... robust.
So I think I'm not lying to anyone who reads it :)
Thank you all,
Mike
On Wed, Jul 4, 2012 at 5:32 PM, Carl Friedrich Bolz
<cfbolz@gmx.de> wrote:
On 07/04/2012 04:19 PM, David Edelsohn wrote:
> On Wed, Jul 4, 2012 at 8:44 AM, Carl Friedrich Bolz <
cfbolz@gmx.de> wrote:
>> However, they don't really precisely answer you question, why tracing JITs
>> are better.
>
> I don't think it is clear that tracing JITs are better.
>
> Tracing often implies some other characteristics and features, such as
> level of inlining, specialization and guards versus arbitrary control
> flow, but method JITs are not prevented from adapting these
> techniques.
>
> The advantages and benefits are a lot subtler than tracing versus method JITs.
Indeed, I don't think anybody really knows the answer yet, under which
circumstances which of the two methods is better. Somebody should try
to do a controlled study .
Cheers,
Carl Friedrich