From 49e06dce074d2f69dafaa5a3e36f6aa444e2a478 Mon Sep 17 00:00:00 2001 From: Justin Ethier Date: Tue, 12 Jun 2018 16:08:02 -0400 Subject: [PATCH] Cleanup comment --- gc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gc.c b/gc.c index 6ce9c04f..74fb790b 100644 --- a/gc.c +++ b/gc.c @@ -1837,8 +1837,8 @@ void gc_collector_trace() // TODO: ideally, want to use a lock-free data structure to prevent // having to use a mutex here. see corresponding code in gc_mark_gray pthread_mutex_lock(&(m->lock)); - // JAE - try doing this loop (majority of tracing) without the lock. - // we shouldn't need to be locked to do it anyway and we still lock + // Try doing this loop (majority of tracing) without the lock. We + // shouldn't need to be locked to do it anyway and we still lock // below as a fail-safe. One potential issue here, will we be broken // if the mark buffer needs to be grown. I think not because we still // will only go as far as the mutator already went with the version of