ruby.git/yjit/src/cruby.rs, branch v4.0.3 The Ruby Programming Language YJIT: Fix not reading locals from `cfp->ep` after `YJIT.enable` and exceptional entry 2026-03-16T18:03:25+00:00 Alan Wu XrXr@users.noreply.github.com 2026-03-12T22:33:00+00:00 8466e93b1d6eb85ad5952ab3a10575fa453e77e2 [Backport #21941] In case of `--yjit-disable`, YJIT only starts to record environment escapes after `RubyVM::YJIT.enable`. Previously we falsely assumed that we always have a full history all the way back to VM boot. This had YJIT install and run code that assume EP=BP when EP≠BP for some exceptional entry into the middle of a running frame, if the environment escaped before `YJIT.enable`. The fix is to reject exceptional entry with an escaped environment. Rename things and explain in more detail how the predicate for deciding to assume EP=BP works. It's quite subtle since it reasons about all parties in the system that push a control frame and then run JIT code. Note that while can_assume_on_stack_env() checks the currently running environment if it so happens to be the one YJIT is compiling against, it can return true for any ISEQ. The check isn't necessary for fixing the bug, and the load bearing part of this patch is the change to exceptional entries. This fix is flat on speed and space on ruby-bench headline benchmarks. Many thanks for the community effort to create a small test case for this bug. 
[Backport #21941]

In case of `--yjit-disable`, YJIT only starts to record environment
escapes after `RubyVM::YJIT.enable`. Previously we falsely assumed that
we always have a full history all the way back to VM boot. This had YJIT
install and run code that assume EP=BP when EP≠BP for some exceptional
entry into the middle of a running frame, if the environment escaped
before `YJIT.enable`.

The fix is to reject exceptional entry with an escaped environment.
Rename things and explain in more detail how the predicate for deciding
to assume EP=BP works. It's quite subtle since it reasons about all
parties in the system that push a control frame and then run JIT code.

Note that while can_assume_on_stack_env() checks the currently running
environment if it so happens to be the one YJIT is compiling against, it
can return true for any ISEQ. The check isn't necessary for fixing the
bug, and the load bearing part of this patch is the change to
exceptional entries.

This fix is flat on speed and space on ruby-bench headline benchmarks.

Many thanks for the community effort to create a small test case for
this bug.
JIT: Move EC offsets to jit_bindgen_constants 2025-12-18T21:43:45+00:00 John Hawthorn john@hawthorn.email 2025-12-18T20:31:34+00:00 73e930f9f911cf71ecb416c3112a7818bae41cd6 Co-authored-by: Alan Wu <alanwu@ruby-lang.org> 
Co-authored-by: Alan Wu <alanwu@ruby-lang.org>
YJIT: Support calling bmethods in Ractors 2025-12-18T21:43:45+00:00 John Hawthorn john@hawthorn.email 2025-12-17T20:08:43+00:00 345ea0c8e18d3ce8fed332137d225769df619f2b Co-authored-by: Luke Gruber <luke.gru@gmail.com> 
Co-authored-by: Luke Gruber <luke.gru@gmail.com>
ZJIT: Add codegen for FixnumDiv (#15452) 2025-12-09T12:41:09+00:00 Abrar Habib 86024593+dddictionary@users.noreply.github.com 2025-12-09T12:41:09+00:00 edca81a1bb72a9dc54a37766d2c80790dec13884 Fixes https://github.com/Shopify/ruby/issues/902 This pull request adds code generation for dividing fixnums. Testing confirms the normal case, flooring, and side-exiting on division by zero. 
Fixes https://github.com/Shopify/ruby/issues/902

This pull request adds code generation for dividing fixnums.
Testing confirms the normal case, flooring, and side-exiting on division by zero.
 ZJIT: Specialize String#<< with Fixnum 2025-12-01T23:19:26+00:00 Max Bernstein ruby@bernsteinbear.com 2025-11-25T03:24:45+00:00 8aed31103874524395912fb7ffaee88b5e59a9c3 Append a codepoint. 
Append a codepoint.
YJIT: Abort expandarray optimization if method_missing is defined 2025-11-26T20:56:27+00:00 Randy Stauner randy@r4s6.net 2025-11-26T02:29:02+00:00 5f55c9c8fb8f401537e7121171747196e66c3ba0 Fixes: [Bug #21707] [AW: rewrote comments] Co-authored-by: Alan Wu <alanwu@ruby-lang.org> 
Fixes: [Bug #21707]
[AW: rewrote comments]
Co-authored-by: Alan Wu <alanwu@ruby-lang.org>
ZJIT: Implement codegen for FixnumMod (#14857) 2025-10-20T21:30:48+00:00 Max Bernstein rubybugs@bernsteinbear.com 2025-10-20T21:30:48+00:00 17368234bfd0b37c58a4b694d764d42e2cad8880 This is mostly to see what happens to the loops-times benchmark. 
This is mostly to see what happens to the loops-times benchmark.
 Add rb_jit_vm_unlock and share it in ZJIT and YJIT 2025-08-29T19:55:14+00:00 Stan Lo stan.lo@shopify.com 2025-08-29T18:16:43+00:00 3f3a54efff040e1f5dbbd296abe9ab0cb9304e4e 






Add rb_jit_vm_lock_then_barrier and share it in ZJIT and YJIT
2025-08-29T19:55:14+00:00

Stan Lo
stan.lo@shopify.com

2025-08-29T18:13:42+00:00

561050496c602ebc41d844db9fee91017f132d3a












Replace ROBJECT_EMBED by ROBJECT_HEAP
2025-08-27T10:41:07+00:00

Jean Boussier
jean.boussier@gmail.com

2025-08-26T15:43:11+00:00

5257e1298c4dc4e854eaa0a9fe5e6dc5c1495c91

The embed layout is way more common than the heap one,
especially since WVA.

I think it makes for more readable code to inverse the
flag.





The embed layout is way more common than the heap one,
especially since WVA.

I think it makes for more readable code to inverse the
flag.