Thanks to visit codestin.com
Credit goes to github.com

Skip to content

ZJIT: setglobal should not return output #13744

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

Merged
merged 2 commits into from
Jun 30, 2025
Merged

Conversation

k0kubun
Copy link
Member

@k0kubun k0kubun commented Jun 30, 2025

This PR fixes a crash in btest test_class.rb.

gen_setglobal() returns an output, so Insn::SetGlobal should be considered to have output to avoid assertion failures.

@k0kubun k0kubun marked this pull request as ready for review June 30, 2025 15:54
@matzbot matzbot requested a review from a team June 30, 2025 15:54
@tekknolagi
Copy link
Contributor

I don't think setglobal has an output -- our SetGlobal pretty neatly maps to setglobal in insns.def, which has no stack output. This may be related to some neighboring instruction though

@k0kubun k0kubun changed the title ZJIT: setglobal has an output ZJIT: setglobal should not return output Jun 30, 2025
Copy link
Contributor

@tekknolagi tekknolagi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with PR title change

@k0kubun k0kubun merged commit 44e4b02 into ruby:master Jun 30, 2025
75 of 79 checks passed
@k0kubun k0kubun deleted the zjit-setglobal branch June 30, 2025 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants