Author: Remi Meier <[email protected]>
Branch: use-gcc
Changeset: r1949:c8524a717c93
Date: 2015-08-27 10:18 +0200
http://bitbucket.org/pypy/stmgc/changeset/c8524a717c93/
Log: remove XXX
diff --git a/c8/stm/finalizer.c b/c8/stm/finalizer.c
--- a/c8/stm/finalizer.c
+++ b/c8/stm/finalizer.c
@@ -486,12 +486,7 @@
LIST_FREE(f->run_finalizers);
}
-/* XXX: can there be a race between _invoke_general_finalizers
- and _commit_finalizer on g_finalizers (+other places?)?
- XXX: what happens in _execute_finalizer if the transaction
- conflicts (or fails to become inevitable) in a finalizer?
- (the run_finalizers list is half-way cleared?)
- XXX: according to translator.backendopt.finalizer, getfield_gc
+/* XXX: according to translator.backendopt.finalizer, getfield_gc
for primitive types is a safe op in light finalizers.
I don't think that's correct in general (maybe if
getfield on *dying obj*).
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
