summaryrefslogtreecommitdiff
path: root/vm.c
diff options
context:
space:
mode:
authork0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-06-23 13:41:06 +0000
committerk0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-06-23 13:41:06 +0000
commit06f54f03039c225c5c0b5d1709865fb4fff02776 (patch)
treee75e84878da6dbf03e16af50c1c5529e86852660 /vm.c
parent359dd59db2512d801bb983f98bede4fc598f139a (diff)
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
Diffstat (limited to 'vm.c')
-rw-r--r--vm.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/vm.c b/vm.c
index 24464a1..3cc0f94 100644
--- a/vm.c
+++ b/vm.c
@@ -2777,7 +2777,7 @@ core_hash_merge_kwd(int argc, VALUE *argv)
static VALUE
mjit_enabled_p(void)
{
- return mjit_init_p ? Qtrue : Qfalse;
+ return mjit_enabled ? Qtrue : Qfalse;
}
extern VALUE mjit_pause(void);