From 48f1395c1d4cd4fe270ecc041830ad613c39194f Mon Sep 17 00:00:00 2001 From: hboehm Date: Thu, 3 Jan 2008 23:05:59 +0000 Subject: [PATCH] 2007-01-03 Hans Boehm * include/gc.h (GC_INIT,GC_init): Update comments. --- ChangeLog | 4 ++++ include/gc.h | 10 ++++------ 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/ChangeLog b/ChangeLog index d131f806..89bd1a99 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2007-01-03 Hans Boehm + + * include/gc.h (GC_INIT,GC_init): Update comments. + 2007-01-03 Hans Boehm (based on a patch from John Bowman, and an ancient patch from Fergus Henderson) diff --git a/include/gc.h b/include/gc.h index 91dc6dc2..14bfa4c3 100644 --- a/include/gc.h +++ b/include/gc.h @@ -237,11 +237,8 @@ GC_API unsigned long GC_time_limit; /* Public procedures */ -/* Initialize the collector. This is only required when using thread-local - * allocation, since unlike the regular allocation routines, GC_local_malloc - * is not self-initializing. If you use GC_local_malloc you should arrange - * to call this somehow (e.g. from a constructor) before doing any allocation. - * For win32 threads, it needs to be called explicitly. +/* Initialize the collector. Portable clients should call GC_INIT() from + * the main program instead. */ GC_API void GC_init(void); @@ -1095,7 +1092,8 @@ GC_API void GC_use_DllMain(void); * no-op and the collector self-initializes. But a number of platforms * make that too hard. * A GC_INIT call is required if the collector is built with THREAD_LOCAL_ALLOC - * defined and the initial allocation call is not to GC_malloc(). + * defined and the initial allocation call is not to GC_malloc() or + * GC_malloc_atomic(). */ #if defined(__CYGWIN32__) || defined (_AIX) /* -- 2.40.0