summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-10-20Fix avg_len_in_yjitAlan Wu
We weren't counting completing an entire method in YJIT as exits so the avg_len_in_yjit for ./miniruby --yjit-call-threshold=1 --yjit-stats -e'def foo; end; foo' was infinite.
2021-10-20Deduplicate side exitsAlan Wu
Send instructions currently generate the exact same side exit twice. Cache the exit the first time we generate it. Also add a comment explaining what side exits do. Closes GH-117.
2021-10-20Info for Fedora and choosing C compilerBenson Muite
2021-10-20Add rb_darray_clear() for Kevin. Fix some warnings.Maxime Chevalier-Boisvert
2021-10-20Add fixes for feedbackAaron Patterson
2021-10-20Use C_ARG_REGS earlierJohn Hawthorn
2021-10-20Add tests against opt_eq side exitsJohn Hawthorn
2021-10-20Remove rb_opt_equality_specializedJohn Hawthorn
2021-10-20String and fixnum equalityJohn Hawthorn
2021-10-20Use method dispatch for opt_eqJohn Hawthorn
2021-10-20Add jit_rb_obj_equalJohn Hawthorn
2021-10-20Count interpreter instructions when -DYJIT_STATS=1Alan Wu
The interpreter instruction count was enabled based on RUBY_DEBUG as opposed to YJIT_STATS. In builds with YJIT_STATS=1 but RUBY_DEBUG=0, the count was not available. Move YJIT_STATS in yjit.h where declarations are expoed to code outside of YJIT. Also reduce the changes made to the interpreter for calling into YJIT's instruction counting function.
2021-10-20Update README.mdMaxime Chevalier-Boisvert
2021-10-20disable yjit when testing mjitAaron Patterson
2021-10-20Update ruby.cMaxime Chevalier-Boisvert
2021-10-20Exit if YJIT and MJIT are both enabledAaron Patterson
YJIT and MJIT can't be running in the same process otherwise they'll clobber each other. We should show an error and exit if they're both enabled.
2021-10-20Prevent stats being enabled late at run-timeMaxime Chevalier-Boisvert
2021-10-20Exit when the object is frozenAaron Patterson
Exit when the object is frozen, also add tests
2021-10-20Add a write barrier to ivar setAaron Patterson
We need to fire the write barrier during ivar set. This function extracts the write barrier function then calls it. Co-Authored-By: John Hawthorn <john@hawthorn.email>
2021-10-20Implement setivar method callseileencodes
2021-10-20Allow calling variadic cfuncs with many argsJohn Hawthorn
We have a check to ensure we don't have to push args on the stack to call a cfunc with many args. However we never need to use the stack for variadic cfuncs, so we shouldn't care about the number of arguments.
2021-10-20Add codegen for rb_true and rb_falseJohn Hawthorn
These are used by .nil? and therefore opt_nil_p
2021-10-20Allow special case of expandarray with nilJohn Hawthorn
2021-10-20Shave a few instructions off of leaveAlan Wu
The code path for leave that returns to the interpreter (gen_leave() -> yjit_gen_leave_exit()) used to have the logic: ``` cfp->sp++; cfp->sp[-1] = return_val; cfp->sp--; return return_val; ``` The SP changes it made was unnecessary and this change removes it. After this change, `leave` doesn't adjust the `cfp->sp` of the caller and only writes `cfp->sp[0]`. To accomodate this in the JIT-to-JIT return case, return stubs have an `sp_offset` of 1. The change removes sp adjustment from the JIT-to-JIT return case, too, making it more efficient. Also, since the C method case of `send` has an `sp_offset` of 1 after the call, this change enables block version sharing.
2021-10-20Use reg1 in GEN_COUNTER_INC to avoid clobbering RAXAlan Wu
2021-10-20Implement newrangeJohn Hawthorn
2021-10-20Additional invokesuper testsJohn Hawthorn
2021-10-20Implement invokesuper using cfp->ep[ME] checkJohn Hawthorn
This fixes and re-enables invokesuper, replacing the existing guards with a guard on the method entry for the EP.
2021-10-20Store block callee_cme in darrayJohn Hawthorn
This allows a block version to have dependencies on multiple CMEs.
2021-10-20Add a small test for the code GCMaxime Chevalier-Boisvert
2021-10-20Use jit_prepare_routine_callJohn Hawthorn
2021-10-20Implement gen_putstringJohn Hawthorn
2021-10-20Add YJIT logoUfuk Kayserilioglu
Adding YJIT logo with a link to https://yjit.org
2021-10-20typo, rename, commentAlan Wu
2021-10-20Avoid immediate side exits in checktypeJohn Hawthorn
Previously checktype only supported heap objects, however it's not uncommon to receive an immediate, for example when string interpolating a Symbol or Integer.
2021-10-20filter out internal events. add comments. reorderAlan Wu
2021-10-20Lock, don't loock.Alan Wu
2021-10-20Only clear the JIT function when we invalidate the entry blockAaron Patterson
We should only clear the JIT function when the entry point is invalidated. Right now we only support compiling functions with a PC offset of zero (functions that take optional parameters can start at non-zero PC), so this patch just checks that the index is 0 before clearing the jit function
2021-10-20Allow to toggle YJIT stats collection from runtimeJean Boussier
For use cases where you want to collect the metrics for a specific piece of code (typically a web request) you can have the stats turned off by default and then turn them on at runtime before executing the code you care about.
2021-10-20fix typoAlan Wu
2021-10-20TracePoint supportAlan Wu
This change fixes some cases where YJIT fails to fire tracing events. Most of the situations YJIT did not handle correctly involves enabling tracing while running inside generated code. A new operation to invalidate all generated code is added, which uses patching to make generated code exit at the next VM instruction boundary. A new routine called `jit_prepare_routine_call()` is introduced to facilitate this and should be used when generating code that could allocate, or could otherwise use `RB_VM_LOCK_ENTER()`. The `c_return` event is fired in the middle of an instruction as opposed to at an instruction boundary, so it requires special handling. C method call return points are patched to go to a fucntion which does everything the interpreter does, including firing the `c_return` event. The generated code for C method calls normally does not fire the event. Invalided code should not change after patching so the exits are not clobbered. A new variable is introduced to track the region of code that should not change.
2021-10-20Redo the ivtable lookp once the ivar is setMaxime Chevalier-Boisvert
2021-10-20Make sure that there is always an index table entry for getivarsMaxime Chevalier-Boisvert
2021-10-20Update READMEMaxime Chevalier-Boisvert
2021-10-20Allow to compile with --yjit-stats support but not the full RUBY_DEBUGJean Boussier
RUBY_DEBUG have a very significant performance overhead. Enough that YJIT with RUBY_DEBUG is noticeably slower than the interpreter without RUBY_DEBUG. This makes it hard to collect yjit-stats in production environments. By allowing to collect JIT statistics without the RUBy_DEBUG overhead, I hope to make such use cases smoother.
2021-10-20Add toregexp to yjiteileencodes
The FIXME is there so we remember to investigate why insns clears the temporary array. Is this necessary? If it's not we can remove it from both. Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>
2021-10-20Use cmov to handle Qundef case in getivar instead of side-exitMaxime Chevalier-Boisvert
2021-10-20Add ASM commentMaxime Chevalier-Boisvert
2021-10-20update README with correct repository URLMike Dalessio
2021-10-20Implement putspecialobjectJohn Hawthorn
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-28 02:10:43 +0000