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

1 files changed, 2 insertions, 2 deletions

diff --git a/mjit.h b/mjit.h
index 964ab388ae..2f9ea85134 100644
--- a/mjit.h
+++ b/mjit.h
@@ -53,7 +53,7 @@ typedef VALUE (*mjit_func_t)(rb_execution_context_t *, rb_control_frame_t *);
 
 RUBY_SYMBOL_EXPORT_BEGIN
 extern struct mjit_options mjit_opts;
-extern int mjit_init_p;
+extern int mjit_enabled;
 
 extern void mjit_add_iseq_to_process(const rb_iseq_t *iseq);
 extern mjit_func_t mjit_get_iseq_func(struct rb_iseq_constant_body *body);
@@ -94,7 +94,7 @@ mjit_exec(rb_execution_context_t *ec)
     long unsigned total_calls;
     mjit_func_t func;
 
-    if (!mjit_init_p)
+    if (!mjit_enabled)
         return Qundef;
 
     iseq = ec->cfp->iseq;