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

bpo-47120: make JUMP_NO_INTERRUPT relative #32221

Merged
merged 10 commits into from Apr 5, 2022

Conversation

iritkatriel
Copy link
Member

@iritkatriel iritkatriel commented Mar 31, 2022

Doc/whatsnew/3.11.rst Outdated Show resolved Hide resolved
Copy link
Member

@brandtbucher brandtbucher left a comment

Nice. These are always tiny jumps too.

@markshannon
Copy link
Member

markshannon commented Apr 1, 2022

This would be more robust, if you handled it the same way as JUMP_FORWARD/JUMP_BACKWARD.
Add a JUMP_NO_INTERRUPT virtual instruction, and let the assembler emit the correct opcode.
JUMP_NO_INTERRUPT forward is just JUMP_FORWARD.

@iritkatriel
Copy link
Member Author

iritkatriel commented Apr 1, 2022

This would be more robust, if you handled it the same way as JUMP_FORWARD/JUMP_BACKWARD. Add a JUMP_NO_INTERRUPT virtual instruction, and let the assembler emit the correct opcode. JUMP_NO_INTERRUPT forward is just JUMP_FORWARD.

Agreed. I'll update this PR after we've merged #32200 because it would clash otherwise.

@iritkatriel iritkatriel changed the title bpo-47120: replace JUMP_NO_INTERRUPT by the relative JUMP_BACKWARD_NO_INTERRUPT bpo-47120: make JUMP_NO_INTERRUPT relative Apr 2, 2022
@markshannon
Copy link
Member

markshannon commented Apr 5, 2022

Looks good.
Feel free to share the new magic number with #32309. One magic number per day should be enough.

@markshannon
Copy link
Member

markshannon commented Apr 5, 2022

@iritkatriel I've leave it up to you to merge this and #32309 in whichever order you prefer

@iritkatriel iritkatriel merged commit 0aa8d5c into python:main Apr 5, 2022
12 checks passed
@iritkatriel iritkatriel deleted the jump_no_interrupt branch May 20, 2022
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.

None yet

6 participants