[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pypy-dev
Subject:    Re: [pypy-dev] Saving and reloading JIT optimizations
From:       David Fraser <davidf () sjsoft ! com>
Date:       2011-08-19 13:50:02
Message-ID: 635fca56-9b4e-4064-ae96-467d77b8e4ba () jackdaw ! local
[Download RAW message or body]



On Friday, August 19, 2011 at 3:40:24 PM, "Harald Armin Massa" \
<chef@ghum.de> wrote:
> > > The pypy JIT takes a while to work out which parts of python code
> > > need optimization etc,
> 
> > No, this is not really doable.   The JIT writes explicitly in the
> > assembler the address of a ton of constants.
> 
> could a special "logging area" be of use? as in
> 
> JIT decides foo_do_something_often() is worthy to be compiled into \
>                 assembler
> -> this decision gets added to the logging area
> 
> on next startup the JIT can read the logging area, for which functions
> compiling is a good idea?

That sounds interesting. But a lot of the JIT advantage seems to be \
cross-function, which might be more complicated right? If something like \
this were to be done perhaps rather than being done on function names it \
could be done by hashing the compiled bytecode it's executing...

David
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev


[prev in list] [next in list] [prev in thread] [next in thread]