I was debugging why a YJIT test added from backport to 3.3.11 with GC.stress fails downstream. This revealed an assumption in the assert_compiles, that the environment is "clean", or as default as possible. `assert_compiles` already san...jprokop (Jarek Prokop)
> but I see that you carry ruby-2.7.0-Initialize-ABRT-hook.patch, which makes the VM use Kernel#require on boot. That might be the source of the interrupt. I have investigated in depth due to another newer test that uses GC.stress in ...jprokop (Jarek Prokop)
While the MR allows to provide the flags in some manner, which is certainly a big part, in the PR there were mentioned some flags that are important to upstream to keep. See comment https://github.com/ruby/ruby/pull/15695#discussion_r266...jprokop (Jarek Prokop)
Ruby at this moment optionally includes Rust bits. Right now this touches mostly YJIT and ZJIT. Rust is a compiled language with various compile flags at various stages and approaches. My ask is to provide a way to instrument compi...jprokop (Jarek Prokop)
Add `rustc_flags` option for configure that appends to RUSTC_FLAGS flags used when compiling with rustc for customizable build flags. It appends to existing defaults in RUSTC_FLAGS. Co-authored-by: Alan Wu <XrXr@users.noreply.github.com>jprokop (Jarek Prokop)
Ephemeral builds at https://copr.fedorainfracloud.org/coprs/jackorp/ruby-3.5/build/9642454/ (logs under `builder-live.log` per Distro/arch combination) with LTO with the patch applied on top of the 00fcef5378 commit are OK. They passed c...jprokop (Jarek Prokop)
Ruby built with LTO (`-flto`) with the -O2 or -O3 optimization causes misbehavior in miniruby. Using -O1 does not result in segfault. Higher optimization is required. Removing `-flto` results in no segfault. Preview1 was OK, after ru...jprokop (Jarek Prokop)
Sent a backport for Ruby 3.4 as well https://github.com/ruby/ruby/pull/12628 as that the Ruby we ship in Fedora in combination with GCC 15 where the warning was encountered.jprokop (Jarek Prokop)
C++ compiler in GCC 15 now generates a warning when trying to include `<cstdbool>`. This file is being included when compiling with C++ compiler from `include/ruby/internal/stdbool.h`. In C++, true, false and bool are keywords so inc...jprokop (Jarek Prokop)