You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Wrong oparg is passed to trace recorder when JUMP_BACKWARD_JIT is preceded by EXTENDED_ARG #152192
To clarify what is happening:
The instruction made of this pair of code units: EXTENDED_ARG 1; JUMP_BACKWARD_JIT 1 has an oparg of 257, but the EXTENDED_ARG part is ignored and _PyJit_TryInitializeTracing gets passed oparg=1.
To clarify what is happening: The instruction made of this pair of code units: EXTENDED_ARG 1; JUMP_BACKWARD_JIT 1 has an oparg of 257, but the EXTENDED_ARG part is ignored and _PyJit_TryInitializeTracing gets passed oparg=1.
Activity
markshannon commentedon Jun 25, 2026
To clarify what is happening:
The instruction made of this pair of code units:
EXTENDED_ARG 1; JUMP_BACKWARD_JIT 1has anopargof 257, but theEXTENDED_ARGpart is ignored and_PyJit_TryInitializeTracinggets passedoparg=1.markshannon commentedon Jun 25, 2026
Please don't dump AI output into the issue.
If you have a working fix, by all means open PR
Codeer22 commentedon Jun 25, 2026
Deleted that
deadlovelll commentedon Jun 25, 2026
Hello! If you don't mind, can i try work on this?
pythongh-152192: Fix JUMP_BACKWARD passing a truncated oparg to the j…
pythongh-152192: Fix JUMP_BACKWARD passing a truncated oparg to the j…
gh-152192: Fix JUMP_BACKWARD passing a truncated oparg to the jit tra…
Merge branch 'main' into maurycy/bye-abba