[pypy-dev] Any publications regarding PyPy / trace-based JIT compiler?
papito.dit at gmail.com
Thu Jul 5 11:54:41 CEST 2012
So, after discussing with a Professor of our Department with a very good
the issue, he basically was in the line of "...JIT design decisions that a
tracing JIT encourages versus
the default design of a method JIT...", but to be more specific on the
advantages he claimed that:
"tracing JITs can discover optimization opportunities in common dynamic
execution paths that are not apparent to a static compiler or a
method-based JIT compiler".
I think this is a nice comment overall, that the PyPy publications and the
features they describe can
back up nicely.
Thank you :)
On Wed, Jul 4, 2012 at 7:21 PM, Berker Peksağ <berker.peksag at gmail.com>wrote:
> On Wed, Jul 4, 2012 at 7:06 PM, Alex Gaynor <alex.gaynor at gmail.com> wrote:
> > On Wed, Jul 4, 2012 at 8:59 AM, Paulo Köch <paulo.koch at gmail.com> wrote:
> >> On Wed, Jul 4, 2012 at 4:49 PM, David Edelsohn <dje.gcc at gmail.com>
> >> > are all method-based.
> >> This needs to be confirmed but, I really think Firefox's TraceMonkey
> >> is a tracing JIT and Chrome's v8 is a method JIT.
> >> _______________________________________________
> >> pypy-dev mailing list
> >> pypy-dev at python.org
> >> http://mail.python.org/mailman/listinfo/pypy-dev
> > Tracemonkey *was* a tracing JIT, at this point it's being (if not has
> > already been) removed in favor of IonMonkey which is a method JIT.
> Yes, it's removed from SpiderMonkey:
> > Alex
> > --
> > "I disapprove of what you say, but I will defend to the death your right
> > say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
> > "The people's good is the highest law." -- Cicero
> > _______________________________________________
> > pypy-dev mailing list
> > pypy-dev at python.org
> > http://mail.python.org/mailman/listinfo/pypy-dev
> pypy-dev mailing list
> pypy-dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pypy-dev