[pypy-commit] stmgc use-gcc: Right now, it doesn't make sense to print the warning when forking,

arigo noreply at buildbot.pypy.org
Thu Jul 2 20:41:03 CEST 2015


Author: Armin Rigo <arigo at tunes.org>
Branch: use-gcc
Changeset: r1892:f29c44d46d58
Date: 2015-07-02 19:43 +0100
http://bitbucket.org/pypy/stmgc/changeset/f29c44d46d58/

Log:	Right now, it doesn't make sense to print the warning when forking,
	because forking is fast enough

diff --git a/c8/stm/forksupport.c b/c8/stm/forksupport.c
--- a/c8/stm/forksupport.c
+++ b/c8/stm/forksupport.c
@@ -20,7 +20,7 @@
     s_mutex_lock();
 
     dprintf(("forksupport_prepare\n"));
-    fprintf(stderr, "[forking: for now, this operation can take some time]\n");
+    //fprintf(stderr, "[forking: for now, this operation can take some time]\n");
 
     stm_thread_local_t *this_tl = NULL;
     stm_thread_local_t *tl = stm_all_thread_locals;


More information about the pypy-commit mailing list