1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Always return jit_entry even if NULL

Browse Source 
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
This commit is contained in:
Aaron Patterson 2025-02-10 12:01:17 -08:00 committed by Aaron Patterson
parent b74077c19e
commit d680a13ad0
Notes: git 2025-02-10 20:50:41 +00:00 
Merged: https://github.com/ruby/ruby/pull/12729
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
vm.c
View File

@ -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)) {