[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:       "Massa, Harald Armin" <chef () ghum ! de>
Date:       2011-08-19 13:40:24
Message-ID: CAMSP2L65W7Y-qJfwuL7Y1L+YchdC2c25f=1mmUcr8JAqc6RV0g () mail ! gmail ! com
[Download RAW message or body]

>> 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?

Harald


-- 
GHUM GmbH
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607

Amtsgericht Stuttgart, HRB 734971
-
persuadere.
et programmare
_______________________________________________
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]