From 06f54f03039c225c5c0b5d1709865fb4fff02776 Mon Sep 17 00:00:00 2001 From: k0kubun Date: Sat, 23 Jun 2018 13:41:06 +0000 Subject: mjit.c: unify the variable name with method name `RubyVM::MJIT.enabled?`. It's set to be TRUE even before initialization is finished. So it was actually not "mjit initialized predicate". This flag is also used to check whether JIT-ed code should be called or not, but I'm going to split the responsibility to another flag. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63732 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- cont.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'cont.c') diff --git a/cont.c b/cont.c index 7c8982087d..634733807a 100644 --- a/cont.c +++ b/cont.c @@ -378,7 +378,7 @@ cont_free(void *ptr) #endif RUBY_FREE_UNLESS_NULL(cont->saved_vm_stack.ptr); - if (mjit_init_p && cont->mjit_cont != NULL) { + if (mjit_enabled && cont->mjit_cont != NULL) { mjit_cont_free(cont->mjit_cont); } /* free rb_cont_t or rb_fiber_t */ @@ -565,7 +565,7 @@ cont_init(rb_context_t *cont, rb_thread_t *th) cont->saved_ec.local_storage = NULL; cont->saved_ec.local_storage_recursive_hash = Qnil; cont->saved_ec.local_storage_recursive_hash_for_trace = Qnil; - if (mjit_init_p) { + if (mjit_enabled) { cont->mjit_cont = mjit_cont_new(&cont->saved_ec); } } -- cgit v1.2.3