<div dir="ltr"><div><div>Hello Bengt,<br><br></div>If I'm not mistaken I think this FAQ item should at least partly answer your question :<br><br><a href="http://pypy.readthedocs.org/en/latest/faq.html#couldn-t-the-jit-dump-and-reload-already-compiled-machine-code">http://pypy.readthedocs.org/en/latest/faq.html#couldn-t-the-jit-dump-and-reload-already-compiled-machine-code</a><br><br></div>Regards<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 25, 2015 at 1:12 AM, Bengt Richter <span dir="ltr"><<a href="mailto:bokr@oz.net" target="_blank">bokr@oz.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 02/24/2015 11:17 PM Maciej Fijalkowski wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Richard.<br>
<br>
<br>
I will respond inline<br>
<br>
On Tue, Feb 24, 2015 at 8:18 PM, Richard Plangger <<a href="mailto:rich@pasra.at" target="_blank">rich@pasra.at</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
hi,<br>
</blockquote></blockquote></span>
[...]<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
(1) Is there a better way to get loops hot?<br>
</blockquote>
<br>
no, not really (you can lower the threshold though, see pypy --jit<br>
help for details, only global)<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
</blockquote></blockquote></span>
PMJI, but I am curious if it would be possible to change pypy to use<br>
mmap'd files for all memory allocations for heaps and stacks<br>
so that the state of hotness and jit state could be captured.<br>
<br>
Files could be virtually large, since UIAM physical allocation does<br>
not occur until write, or at least is controllable.<br>
<br>
The idea then would be to write programs with a warm-up prelude function,<br>
and then have a checkpointing module with a method that could write a<br>
specially stubbed ELF file along with all the file data, so that the ELF<br>
would be an executable whose _start would get back to the checkpoint module<br>
where everything would be restored as it was checkpointed, and execution<br>
would continue as if just returning from the call to the checkpointing method,<br>
which would be after the forced warmup prelude.<br>
<br>
Sorry if I am intruding.<br>
Regards,<br>
Bengt Richter<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
pypy-dev mailing list<br>
<a href="mailto:pypy-dev@python.org" target="_blank">pypy-dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/pypy-dev" target="_blank">https://mail.python.org/<u></u>mailman/listinfo/pypy-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Vincent Legoll</div>
</div>