-
Notifications
You must be signed in to change notification settings - Fork 63
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: github/ruby
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: ruby/ruby
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 25 files changed
- 5 contributors
Commits on Jul 30, 2025
-
YJIT: Remove a dead test for getinlinecaches (ruby#14033)
The test was added in ruby#5221 4 years ago but: 1. The insn it targets was removed in 2022 in ruby#6187 2. The YJIT API `blocks_for` seems to be dropped in 2022 when it switched to use Rust in ruby#5826 So this test has not been run in more than 3 years and can't be run anymore. I think we can remove it.
Configuration menu - View commit details
-
Copy full SHA for 4263c49 - Browse repository at this point
Copy the full SHA 4263c49View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2cd10de - Browse repository at this point
Copy the full SHA 2cd10deView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0aac763 - Browse repository at this point
Copy the full SHA 0aac763View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9a30554 - Browse repository at this point
Copy the full SHA 9a30554View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7b10dbd - Browse repository at this point
Copy the full SHA 7b10dbdView commit details -
Configuration menu - View commit details
-
Copy full SHA for 096d48d - Browse repository at this point
Copy the full SHA 096d48dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0f7ee8e - Browse repository at this point
Copy the full SHA 0f7ee8eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8c73b10 - Browse repository at this point
Copy the full SHA 8c73b10View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1b700c5 - Browse repository at this point
Copy the full SHA 1b700c5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 75f25e5 - Browse repository at this point
Copy the full SHA 75f25e5View commit details -
Don't check the symbol's fstr at shutdown
During Ruby's shutdown, we no longer need to check the fstr of the symbol because we don't use the fstr anymore for freeing the symbol. This can also fix the following ASAN error: ==2721247==ERROR: AddressSanitizer: use-after-poison on address 0x75fa90a627b8 at pc 0x64a7b06fb4bc bp 0x7ffdf95ba9b0 sp 0x7ffdf95ba9a8 READ of size 8 at 0x75fa90a627b8 thread T0 #0 0x64a7b06fb4bb in RB_BUILTIN_TYPE include/ruby/internal/value_type.h:191:30 #1 0x64a7b06fb4bb in rb_gc_shutdown_call_finalizer_p gc.c:357:18 #2 0x64a7b06fb4bb in rb_gc_impl_shutdown_call_finalizer gc/default/default.c:3045:21 #3 0x64a7b06fb4bb in rb_objspace_call_finalizer gc.c:1739:5 #4 0x64a7b06ca1b2 in rb_ec_finalize eval.c:165:5 #5 0x64a7b06ca1b2 in rb_ec_cleanup eval.c:256:5 #6 0x64a7b06c98a3 in ruby_cleanup eval.c:179:12
Configuration menu - View commit details
-
Copy full SHA for 7cece23 - Browse repository at this point
Copy the full SHA 7cece23View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master