From d680a13ad061eeb562b1df7c11d094e6984789ce Mon Sep 17 00:00:00 2001 From: Aaron Patterson Date: Mon, 10 Feb 2025 12:01:17 -0800 Subject: [PATCH] Always return jit_entry even if NULL We can just always return the jit_entry since it will be initialized to NULL. There is no reason to specifically return NULL if yjit / rjit are disabled --- vm.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/vm.c b/vm.c index 87e6e9fecd..e7604bb258 100644 --- a/vm.c +++ b/vm.c @@ -435,12 +435,9 @@ jit_compile(rb_execution_context_t *ec) const rb_iseq_t *iseq = ec->cfp->iseq; struct rb_iseq_constant_body *body = ISEQ_BODY(iseq); bool yjit_enabled = rb_yjit_enabled_p; - if (!(yjit_enabled || rb_rjit_call_p)) { - return NULL; - } // Increment the ISEQ's call counter and trigger JIT compilation if not compiled - if (body->jit_entry == NULL) { + if (body->jit_entry == NULL && (yjit_enabled || rb_rjit_call_p)) { body->jit_entry_calls++; if (yjit_enabled) { if (rb_yjit_threshold_hit(iseq, body->jit_entry_calls)) {