[issue47177] Frames should store next_instr instead of lasti

Change by Brandt Bucher : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue47177] Frames should store next_instr instead of lasti

Brandt Bucher added the comment: New changeset ef6a482b0285870c45f39c9b17ed827362b334ae by Brandt Bucher in branch 'main': bpo-47177: Replace `f_lasti` with `prev_instr` (GH-32208) https://github.com/python/cpython/commit/ef6a482b0285870c45f39c9b17ed827362b334ae --

[issue47177] Frames should store next_instr instead of lasti

Change by Brandt Bucher : -- keywords: +patch pull_requests: +30283 pull_request: https://github.com/python/cpython/pull/32208 ___ Python tracker ___ __

[issue47177] Frames should store next_instr instead of lasti

New submission from Brandt Bucher : Rather than maintaining the offset of the "last instruction" (`f_lasti`), interpreter frames should instead just maintain a pointer to the true next instruction. This has several benefits, most notably reducing the register pressure associated with loading