diff options
author | Takashi Kokubun <takashikkbn@gmail.com> | 2019-05-15 23:13:36 -0700 |
---|---|---|
committer | Takashi Kokubun <takashikkbn@gmail.com> | 2019-05-15 23:14:07 -0700 |
commit | 82332c7d8b17b610a347f7c804219c7fcb702d23 (patch) | |
tree | d7abbb48b3487e6daf014e4f7c848a5fc8d5fff3 /mjit.c | |
parent | 18e43e823106f15c8aaceb1f56874bdf67bc36a3 (diff) |
Rename mjit_gc_finish_hook to mjit_gc_exit_hook
because @ko1 said "gc_finish" is confusing like a finish of entire GC
process
Diffstat (limited to 'mjit.c')
-rw-r--r-- | mjit.c | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -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 |