Ruby Issue Tracking System

07/04/2026

04:30 PM Ruby Bug #22178 (Closed): Regexp#== regression: regexps built via the `rb_reg_new` C API are no longer equal to an identical literal

On current master, two `Regexp` objects that have the same options, the same regexp encoding (`Regexp#encoding`),
and byte-identical sources are no longer `==` if their *source strings* have different encodings (e.g. `ASCII-8BIT` vs `US... watson1978 (Shizuo Fujita)

09/19/2025

11:22 AM Ruby Bug #21611: Ruby 3.4.6 can't be built with GCC 15.2.1

Attached full build logs. watson1978 (Shizuo Fujita)

11:07 AM Ruby Bug #21611 (Closed): Ruby 3.4.6 can't be built with GCC 15.2.1

Arch Linux provides GCC 15.2.1.
https://archlinux.org/packages/core/x86_64/gcc/
When I build Ruby 3.4.6 with GCC 15.2.1, it cause error:
### How to Reproduce
Here is a Dockerfile to reproduce the error:
```
FROM archlinux:lat... watson1978 (Shizuo Fujita)

08/21/2025

01:18 PM Ruby Bug #21547: SEGV after 2083fa commit

Thanks. It works well! watson1978 (Shizuo Fujita)

10:09 AM Ruby Bug #21547: SEGV after 2083fa commit

We are running tests using Ruby HEAD on Linux, macOS, and Windows platforms.
https://github.com/fluent/fluentd/actions/runs/17022072274
The SEGV are caused on each platforms... watson1978 (Shizuo Fujita)

08/20/2025

02:27 AM Ruby Bug #21547 (Closed): SEGV after 2083fa commit

I am maintaining [Fluentd](https://github.com/fluent/fluentd).
When I run Fluentd's unit tests after [2083fa](https://github.com/ruby/ruby/commit/2083fa89fc29005035c1a098185c4b707686a437) commit,
Ruby causes SEGV.
```
$ git clone -... watson1978 (Shizuo Fujita)

05/05/2025

09:40 AM Ruby Feature #21308 (Open): Replacing the Float#to_s (dtoa.c) implementation with a modern algorithm

This is a feature request to replace Ruby's `Float#to_s` implementation with a modern high-performance float-to-string conversion algorithm such as Grisu.
Currently, `Float#to_s` in Ruby uses the BSD-derived implementation in [missing... watson1978 (Shizuo Fujita)

02/13/2025

10:53 AM Ruby Bug #21132 (Closed): Changed postposition `rescue` and `if` behavior since Ruby 3.4

watson1978 (Shizuo Fujita)

10:52 AM Ruby Bug #21132: Changed postposition `rescue` and `if` behavior since Ruby 3.4

My problem will be solved by https://github.com/ruby/ruby/commit/c2908613368b2ae404d094a15df61d830fc46dc9
Thanks watson1978 (Shizuo Fujita)

02:44 AM Ruby Bug #21132: Changed postposition `rescue` and `if` behavior since Ruby 3.4

When I switched parser to parse.y, it has same result with Ruby 3.3.
```
[~/tmp]$ ruby -v --parser=parse.y t.rb
ruby 3.4.1 (2024-12-25 revision 48d4efcb85) [x86_64-linux]
"fugafuga"
[~/tmp]$ ruby -v --parser=prism t.rb
ruby 3.4.1... watson1978 (Shizuo Fujita)