Author: Armin Rigo <[email protected]>
Branch: jitypes2
Changeset: r44612:936c8deb74ab
Date: 2011-05-31 15:20 +0200
http://bitbucket.org/pypy/pypy/changeset/936c8deb74ab/
Log: Right now I believe that this comment is nonsense. (Not really
tested either way...)
diff --git a/pypy/jit/backend/x86/assembler.py
b/pypy/jit/backend/x86/assembler.py
--- a/pypy/jit/backend/x86/assembler.py
+++ b/pypy/jit/backend/x86/assembler.py
@@ -320,23 +320,14 @@
next.prev = new
# and now release the GIL
before = rffi.aroundstate.before
- # Store a flag (by abuse in new+2*WORD) that tells if we must
- # call the "after" function or not. The issue is that the
- # before/after fields can be set at a random point during the
- # execution, and we should not call the "after" function if we
- # did not call the "before" function. It works by assuming that
- # before/after start out being None/None, and are later set (once
- # only) to some pair of functions.
- css[2] = int(bool(before))
if before:
before()
@staticmethod
def _reopen_stack_asmgcc(css):
# first reacquire the GIL
- if css[2]:
- after = rffi.aroundstate.after
- assert after
+ after = rffi.aroundstate.after
+ if after:
after()
# similar to trackgcroot.py:pypy_asm_stackwalk, second part
from pypy.rpython.memory.gctransform import asmgcroot
_______________________________________________
pypy-commit mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pypy-commit
