[pypy-svn] commit/pypy: arigo: Mostly for symmetry reasons, also call keep_loop_alive() in

Bitbucket commits-noreply at bitbucket.org
Sun Dec 19 12:37:52 CET 2010

1 new changeset in pypy:

changeset:   r40124:5be1f80cec63
user:        arigo
date:        2010-12-19 12:37:38
summary:     Mostly for symmetry reasons, also call keep_loop_alive() in
send_bridge_to_backend().  One issue this fixes could be if we
attach the bridge to a loop that is old enough to go away very soon,
but the bridge itself is jumping somewhere else, so that the code
in warmstate.py wouldn't immediately keep that loop alive.
affected #:  1 file (166 bytes)

--- a/pypy/jit/metainterp/compile.py	Sat Nov 06 23:42:23 2010 +0000
+++ b/pypy/jit/metainterp/compile.py	Sun Dec 19 12:37:38 2010 +0100
@@ -167,6 +167,9 @@
     if not we_are_translated():
     metainterp_sd.log("compiled new bridge")
+    if metainterp_sd.warmrunnerdesc is not None:    # for tests
+        metainterp_sd.warmrunnerdesc.memory_manager.keep_loop_alive(
+            original_loop_token)
 # ____________________________________________________________

Repository URL: https://bitbucket.org/pypy/pypy/


This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

More information about the Pypy-commit mailing list