ruby.git/zjit/src/gc.rs, branch v4.0.4

ZJIT: Add a VALUE#write_barrier helper method to deduplicate logic

2025-12-16T20:00:27+00:00

ZJIT: Guard other calls to rb_gc_writebarrier() with a !special_const_p() check

2025-12-16T20:00:27+00:00

ZJIT: Re-compile ISEQs invalidated by PatchPoint (#15459)

2025-12-11T00:07:39+00:00

ZJIT: Carve out IseqPayload into a separate module (#15098)

2025-11-07T16:54:21+00:00

YJIT: ZJIT: Fix rustdoc dead links

2025-10-12T04:51:59+00:00

ZJIT: Add `NoSingletonClass` patch point (#14680)

2025-10-02T16:03:25+00:00

* ZJIT: Add NoSingletonClass patch point

This patch point makes sure that when the object has a singleton class,
the JIT code is invalidated. As of now, this is only needed for C call
optimization.

In YJIT, the singleton class guard only applies to Array, Hash, and String.
But in ZJIT, we may optimize C calls from gems (e.g. `sqlite3`). So the
patch point needs to be applied to a broader range of classes.

* ZJIT: Only generate NoSingletonClass guard when the type can have singleton class

* ZJIT: Update or forget NoSingletonClass patch point when needed

ZJIT: Add --zjit-trace-exits (#14640)

2025-09-30T15:55:33+00:00

Add side exit tracing functionality for ZJIT

ZJIT: Remove RefCell from IseqCall

2025-09-29T17:04:55+00:00

No point taking the panic risks with RefCell when most fields in it are
already in a Cell. Put `iseq` in a Cell and we no longer need the
wrapping. Saves memory, too.

ZJIT: Compile ISEQ with optional arguments (#14653)

2025-09-25T23:57:23+00:00

ZJIT: Remove dead CMEs from `Invariants`

2025-09-25T22:36:58+00:00