GH-100982: Restrict FOR_ITER_RANGE to a single instruction to allow instrumentation.#101985
Uh oh!
There was an error while loading. Please reload this page.
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.
Currently
FOR_ITER_RANGEis a superinstruction, specializing aFOR_ITER; STORE_FASTpair.This is a problem for instrumentation which assumes the PEP 659 promise that all specializations are atomic.
This PR restricts
FOR_ITER_RANGEto a single instruction.