ruby.git/Cargo.toml, branch v4.0.4 The Ruby Programming Language JITs: Drop cargo and use just rustc for release combo build 2025-12-10T21:35:00+00:00 Alan Wu XrXr@users.noreply.github.com 2025-12-09T03:25:05+00:00 029a48176cf9fd367d52d8c9f87cb9f77d425a43 So we don't expose builders to network flakiness which cannot be worked around using cargo's --offline flag. 
So we don't expose builders to network flakiness which cannot be worked
around using cargo's --offline flag.
ZJIT: Move jit.rs to ruby.rs and create a shared crate `jit` 2025-09-12T04:51:47+00:00 Aiden Fox Ivey aiden.foxivey@shopify.com 2025-09-12T03:32:06+00:00 f75e1cb362f57aa9e18c42026adec39b86d4e5c6 * ruby.rs should hold the main entrypoint to YJIT and ZJIT * The crate jit will hold code shared between them 
* ruby.rs should hold the main entrypoint to YJIT and ZJIT
* The crate jit will hold code shared between them
YJIT: Side-exit on String#dup when it's not leaf (#13921) 2025-07-16T22:59:32+00:00 Takashi Kokubun takashi.kokubun@shopify.com 2025-07-16T22:59:32+00:00 571a8d2753ab252b45afba862fc5917c1b8a1e09 * YJIT: Side-exit on String#dup when it's not leaf * Use an enum instead of a macro for bindgen 
* YJIT: Side-exit on String#dup when it's not leaf

* Use an enum instead of a macro for bindgen
 YJIT: Disable the runtime_checks feature temporarily 2025-07-16T18:10:22+00:00 Alan Wu XrXr@users.noreply.github.com 2025-07-16T01:19:47+00:00 ccbbe06a0277db74cfbf7dc1f26722cbf4904b72 The stack canary gets killed in test_yjit.rb:224 for some reason. Needs investigation. Example CI failure: https://github.com/ruby/ruby/actions/runs/16307837724/job/46057558066 
The stack canary gets killed in test_yjit.rb:224 for some reason. Needs
investigation. Example CI failure:
https://github.com/ruby/ruby/actions/runs/16307837724/job/46057558066
ZJIT: Have `make zjit-test` use the same Cargo features as miniruby 2025-07-16T18:10:22+00:00 Alan Wu XrXr@users.noreply.github.com 2025-07-15T21:16:57+00:00 5ee3937a9c8f75d07f4919f64decd0b850abefe0 This is so that e.g. building with `--enable-zjit=dev` will test with the disassembly feature. It makes more sense, saves on build time and reveals that `backend::arm64::tests::sp_movements_are_single_instruction` was in fact failing with the `disasm` feature. 
This is so that e.g. building with `--enable-zjit=dev` will test with the
disassembly feature. It makes more sense, saves on build time and
reveals that
`backend::arm64::tests::sp_movements_are_single_instruction` was in
fact failing with the `disasm` feature.
ZJIT: Propagate disasm feature to ZJIT and YJIT (#13372) 2025-05-19T17:34:29+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-05-19T17:34:29+00:00 a7ef9a44a6e072bf3b72f2071195da661ddde8d1 Co-authored-by: Alan Wu <alansi.xingwu@shopify.com> 
Co-authored-by: Alan Wu <alansi.xingwu@shopify.com>
 YJIT: ZJIT: Allow both JITs in the same build 2025-05-14T15:39:03+00:00 Alan Wu XrXr@users.noreply.github.com 2025-05-06T15:19:36+00:00 92b218fbc379fe85792eb060b71520e271971335 This commit allows building YJIT and ZJIT simultaneously, a "combo build". Previously, `./configure --enable-yjit --enable-zjit` failed. At runtime, though, only one of the two can be enabled at a time. Add a root Cargo workspace that contains both the yjit and zjit crate. The common Rust build integration mechanisms are factored out into defs/jit.mk. Combo YJIT+ZJIT dev builds are supported; if either JIT uses `--enable-*=dev`, both of them are built in dev mode. The combo build requires Cargo, but building one JIT at a time with only rustc in release build remains supported. 
This commit allows building YJIT and ZJIT simultaneously, a "combo
build". Previously, `./configure --enable-yjit --enable-zjit` failed. At
runtime, though, only one of the two can be enabled at a time.

Add a root Cargo workspace that contains both the yjit and zjit crate.
The common Rust build integration mechanisms are factored out into
defs/jit.mk.

Combo YJIT+ZJIT dev builds are supported; if either JIT uses
`--enable-*=dev`, both of them are built in dev mode.

The combo build requires Cargo, but building one JIT at a time with only
rustc in release build remains supported.