From 5ee256da687f080f8ec0b12c10fc2592020e4872 Mon Sep 17 00:00:00 2001
From: k0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>
Date: Fri, 29 Mar 2019 14:08:51 +0000
Subject: 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
---
 mjit.c | 6 ------
 1 file changed, 6 deletions(-)

(limited to 'mjit.c')

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");
-- 
cgit v1.2.3