[pypy-commit] stmgc default: Do we need to trace at all? The tests pass like this
arigo
noreply at buildbot.pypy.org
Sat Jul 6 11:10:24 CEST 2013
Author: Armin Rigo <arigo at tunes.org>
Branch:
Changeset: r351:840ac0a8867a
Date: 2013-07-06 11:07 +0200
http://bitbucket.org/pypy/stmgc/changeset/840ac0a8867a/
Log: Do we need to trace at all? The tests pass like this
diff --git a/c4/gcpage.c b/c4/gcpage.c
--- a/c4/gcpage.c
+++ b/c4/gcpage.c
@@ -225,8 +225,8 @@
id_copy->h_tid |= GCFLAG_VISITED;
/* XXX: may not always need tracing? */
- if (!(id_copy->h_tid & GCFLAG_STUB))
- gcptrlist_insert(&objects_to_trace, id_copy);
+ //if (!(id_copy->h_tid & GCFLAG_STUB))
+ // gcptrlist_insert(&objects_to_trace, id_copy);
}
else {
/* prebuilt originals won't get collected anyway
More information about the pypy-commit
mailing list