Author: Armin Rigo <[email protected]>
Branch:
Changeset: r76552:058b23577be0
Date: 2015-03-24 21:05 +0100
http://bitbucket.org/pypy/pypy/changeset/058b23577be0/
Log: The weakref issue was resolved at the cost of
weakref.getweakrefcount & co
diff --git a/pypy/doc/stm.rst b/pypy/doc/stm.rst
--- a/pypy/doc/stm.rst
+++ b/pypy/doc/stm.rst
@@ -155,7 +155,8 @@
show up occasionally elsewhere with accesses to some external
resources, where the (apparent) serialized order doesn't match the
underlying (multithreading) order. These are bugs (partially fixed
- already in ``stmgc-c8``).
+ already in ``stmgc-c8``). Also, debugging helpers like
+ ``weakref.getweakrefcount()`` might give wrong answers.
* The STM system is based on very efficient read/write barriers, which
are mostly done (their placement could be improved a bit in
@@ -380,10 +381,7 @@
Note that Python is a complicated language; there are a number of less
common cases that may cause conflict (of any kind) where we might not
expect it at priori. In many of these cases it could be fixed; please
-report any case that you don't understand. (For example, so far,
-creating a weakref to an object requires attaching an auxiliary
-internal object to that object, and so it can cause write-write
-conflicts.)
+report any case that you don't understand.
Atomic sections
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
