summaryrefslogtreecommitdiff
path: root/thread_local_alloc.c
diff options
context:
space:
mode:
authorhboehm <hboehm>2008-10-22 03:06:28 +0200
committerIvan Maidanski <ivmai@mail.ru>2011-07-26 19:06:43 +0200
commit4e7edff29276d81c29483ea68012333dca2f787b (patch)
tree65af7e9a797cc11e0397715778756af0f277c425 /thread_local_alloc.c
parentb91f19d0827fa88110be7f9c8fee7edf086c5376 (diff)
2008-10-21 Hans Boehm <Hans.Boehm@hp.com> (Really Ivan Maidanski)
* include/private/gc_locks.h, include/private/gc_pmark.h, include/private/gc_priv.h, include/private/gcconfig.h, mach_dep.c, mark_rts.c, misc.c, os_dep.c, pthread_stop_world.c, pthread_support.c, thread_local_alloc.c, typd_mlc.c, win32_threads.c: Fix comments.
Diffstat (limited to 'thread_local_alloc.c')
-rw-r--r--thread_local_alloc.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/thread_local_alloc.c b/thread_local_alloc.c
index 8372c1e..46064d8 100644
--- a/thread_local_alloc.c
+++ b/thread_local_alloc.c
@@ -225,8 +225,8 @@ extern int GC_gcj_kind;
/* fundamental issue is that we may end up marking a free list, which */
/* has freelist links instead of "vtable" pointers. That is usually */
/* OK, since the next object on the free list will be cleared, and */
-/* will thus be interpreted as containg a zero descriptor. That's fine */
-/* if the object has not yet been initialized. But there are */
+/* will thus be interpreted as containing a zero descriptor. That's */
+/* fine if the object has not yet been initialized. But there are */
/* interesting potential races. */
/* In the case of incremental collection, this seems hopeless, since */
/* the marker may run asynchronously, and may pick up the pointer to */