From 82332c7d8b17b610a347f7c804219c7fcb702d23 Mon Sep 17 00:00:00 2001 From: Takashi Kokubun Date: Wed, 15 May 2019 23:13:36 -0700 Subject: Rename mjit_gc_finish_hook to mjit_gc_exit_hook because @ko1 said "gc_finish" is confusing like a finish of entire GC process --- mjit.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'mjit.c') diff --git a/mjit.c b/mjit.c index a4550e922c..9142e92616 100644 --- a/mjit.c +++ b/mjit.c @@ -99,15 +99,15 @@ mjit_gc_start_hook(void) // Send a signal to workers to continue iseq compilations. It is // called at the end of GC. void -mjit_gc_finish_hook(void) +mjit_gc_exit_hook(void) { if (!mjit_enabled) return; - CRITICAL_SECTION_START(4, "mjit_gc_finish_hook"); + CRITICAL_SECTION_START(4, "mjit_gc_exit_hook"); in_gc = false; verbose(4, "Sending wakeup signal to workers after GC"); rb_native_cond_broadcast(&mjit_gc_wakeup); - CRITICAL_SECTION_FINISH(4, "mjit_gc_finish_hook"); + CRITICAL_SECTION_FINISH(4, "mjit_gc_exit_hook"); } // Deal with ISeq movement from compactor -- cgit v1.2.3