Author: Armin Rigo <ar...@tunes.org>
Branch: guard-compatible
Changeset: r90039:583cbba30cdb
Date: 2017-02-10 17:46 +0100
http://bitbucket.org/pypy/pypy/changeset/583cbba30cdb/

Log:    fix at least for backend/llsupport/test/test_zrpy_gc_direct.py

diff --git a/rpython/jit/metainterp/compile.py 
b/rpython/jit/metainterp/compile.py
--- a/rpython/jit/metainterp/compile.py
+++ b/rpython/jit/metainterp/compile.py
@@ -1121,6 +1121,7 @@
 
     _compatibility_conditions = None
     other_compat_conditions = []
+    fallback_jump_target = 0
 
     def __init__(self):
         # XXX think about what is being kept alive here
@@ -1134,7 +1135,8 @@
         # to decide on
         # XXX it would be better to patch the guard properly in the backend,
         # but later
-        self.fallback_jump_target = 0
+        #self.fallback_jump_target = 0 (set on the class, annotator trick in
+        #                            case we don't see any 
GuardCompatibleDescr)
         # the next two attributes are for tracking where the guarded value came
         # from
         self.source_failarg_index = -1
_______________________________________________
pypy-commit mailing list
pypy-commit@python.org
https://mail.python.org/mailman/listinfo/pypy-commit

Reply via email to