diff options
| author | k0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2018-10-07 04:17:59 +0000 |
|---|---|---|
| committer | k0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2018-10-07 04:17:59 +0000 |
| commit | e889fad86c848a15897e246d92a1b8a8d7baaeb5 (patch) | |
| tree | 829b60da286751ccf0b8560cee81b6f237722a27 /golf_prelude.rb | |
| parent | b50955fdb8a0be9ef896c239d12c77995a54e51d (diff) | |
| download | ruby-e889fad86c848a15897e246d92a1b8a8d7baaeb5.tar.gz | |
mjit.h: call compiled code immediately
after the first compilation on --jit-wait.
Previously the assignment to `func` didn't have meaning for the behavior,
and the compiled code wasn't called immediately after the synchronous
compilation. It wasn't intentional.
Fixing this issue without impacting performance without --jit-wait is
not so obvious. Adding branch or goto to call func in mjit_exec spoiled
the performance without --jit-wait. Instead of that, I called the func
inside mjit_wait_call() (former mjit_get_iseq_func()) which is never
inlined to mjit_exec(). Thanks to that, this commit has no impact for
normal performance.
mjit.c: ditto
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64929 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'golf_prelude.rb')
0 files changed, 0 insertions, 0 deletions