Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

YJIT: Fix return type of Integer#/ with T_FIXNUM inputs #8250

Merged
merged 1 commit into from Aug 18, 2023

Conversation

XrXr
Copy link
Member

@XrXr XrXr commented Aug 18, 2023

Issue found by running ruby/spec with --yjit-verify-ctx. Thanks!

Issue found by running ruby/spec with `--yjit-verify-ctx`. Thanks!
@matzbot matzbot requested a review from a team August 18, 2023 15:39
@maximecb
Copy link
Contributor

Is this related to the error reported by Kokubun?

https://github.com/ruby/ruby/actions/runs/5896874188/job/15995521718

@noahgibbs
Copy link
Contributor

noahgibbs commented Aug 18, 2023

This is definitely more correct, but I wonder if it will have knock-on effects with performance.

(Edit to add: but we should still 100% do it. Incorrect is bad.)

@XrXr
Copy link
Member Author

XrXr commented Aug 18, 2023

Is this related to the error reported by Kokubun?

Probably not, the code in the stack trace don't use division. I was trying to recreate that failure locally and ran into this issue instead. I also found another --yjit-verify-ctx issue I'm looking into, but that one also seems unrelated.

@XrXr XrXr merged commit 4524aeb into ruby:master Aug 18, 2023
91 of 93 checks passed
@XrXr XrXr deleted the yjit-fix-fixnumwrong-type branch August 18, 2023 16:17
@maximecb
Copy link
Contributor

This is definitely more correct, but I wonder if it will have knock-on effects with performance.

Unlikely because division is fairly rare in practice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants