Skip to content

[pull] master from ruby:master#1013

Merged
pull[bot] merged 14 commits into
turkdevops:masterfrom
ruby:master
May 14, 2026
Merged

[pull] master from ruby:master#1013
pull[bot] merged 14 commits into
turkdevops:masterfrom
ruby:master

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented May 14, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

jhawthorn and others added 14 commits May 14, 2026 07:07
Co-authored-by: Jean Boussier <byroot@ruby-lang.org>
../../../ext/digest/digest.c: In function ‘get_digest_base_metadata’:
  ../../../ext/digest/digest.c:587:12: warning: ‘obj’ may be used uninitialized [-Wmaybe-uninitialized]
    587 |     algo = get_metadata_ptr(obj);
        |            ^~~~~~~~~~~~~~~~~~~~~
  ../../../ext/digest/digest.c:574:11: note: ‘obj’ was declared here
    574 |     VALUE obj;
        |           ^~~

ruby/digest@edaafc2157
FL_TEST -> FL_TEST_RAW
FL_SET  -> FL_SET_RAW

I was seeing bad performance on the ruby-bench getivar-module benchmark
when using yjit. This was with other changes in a branch, but changes
totally unrelated to accessing ivars on a class or using boxes. The
change to RCLASS_PRIME_CLASSEXT_WRITABLE_P was the one that made the
difference, but I changed a couple of other FL_SET uses as well. This
change reduced the benchmark runs from 60ms to 40ms.
* The newly-released Ruby 4.0.4 fails that spec otherwise.
@pull pull Bot locked and limited conversation to collaborators May 14, 2026
@pull pull Bot added the ⤵️ pull label May 14, 2026
@pull pull Bot merged commit a8bcae0 into turkdevops:master May 14, 2026
1 of 3 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants