aboutsummaryrefslogtreecommitdiffstats
path: root/mjit.c
diff options
context:
space:
mode:
authork0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2019-03-29 14:08:51 +0000
committerk0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2019-03-29 14:08:51 +0000
commit5ee256da687f080f8ec0b12c10fc2592020e4872 (patch)
treef4117e13c300f9353a0915e12a255382af9f0876 /mjit.c
parentb03c11a337c53c219a840eed4569e411289f0ddd (diff)
downloadruby-5ee256da687f080f8ec0b12c10fc2592020e4872.tar.gz
Prevent mjit length counters from being 0
It seems that `debug_counter_show_results_at_exit` could be called earlier than `mjit_finish` sometimes. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67380 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'mjit.c')
-rw-r--r--mjit.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/mjit.c b/mjit.c
index 710f370947..a1c8f238c2 100644
--- a/mjit.c
+++ b/mjit.c
@@ -781,12 +781,6 @@ mjit_finish(bool close_handle_p)
if (!mjit_enabled)
return;
-#if USE_DEBUG_COUNTER
- rb_debug_counter_add(RB_DEBUG_COUNTER_mjit_length_unit_queue, unit_queue.length, 1);
- rb_debug_counter_add(RB_DEBUG_COUNTER_mjit_length_active_units, active_units.length, 1);
- rb_debug_counter_add(RB_DEBUG_COUNTER_mjit_length_compact_units, compact_units.length, 1);
-#endif
-
/* Wait for pch finish */
verbose(2, "Stopping worker thread");
CRITICAL_SECTION_START(3, "in mjit_finish to wakeup from pch");