[3.10] bpo-46724: Use JUMP_ABSOLUTE for all backward jumps. (GH-31326)
#31354
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Backport of GH-31326, plus supporting code from 3.11.
markshannon
changed the title
JUMP_ABSOLUTE for all backward jumps. (GH-31326)JUMP_ABSOLUTE for all backward jumps. (GH-31326)
|
LGTM Thanks for the backport @markshannon |
pablogsal
approved these changes
Feb 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of GH-31326, plus supporting code from 3.11.
Backports the whole
normalize_jumps()function from 3.11, as that seems the cleanest way to do this.Consequently this PR also converts forward
JUMP_ABSOLUTEtoJUMP_FORWARD, which should be harmless.https://bugs.python.org/issue46724