[issue41463] Avoid duplicating jump information from opcode.py in compile.c

Mark Shannon added the comment: I don't think we want to backport it -- stage: patch review -> resolved status: pending -> closed ___ Python tracker ___

[issue41463] Avoid duplicating jump information from opcode.py in compile.c

Irit Katriel added the comment: This seems complete, unless you still want to backport? -- nosy: +iritkatriel resolution: -> fixed status: open -> pending ___ Python tracker

[issue41463] Avoid duplicating jump information from opcode.py in compile.c

Mark Shannon added the comment: New changeset 582aaf19e8b94a70c1f96792197770d604ba0fdf by Mark Shannon in branch 'master': bpo-41463: Generate information about jumps from 'opcode.py' rather than duplicating it in 'compile.c' (GH-21714)

[issue41463] Avoid duplicating jump information from opcode.py in compile.c

Change by Mark Shannon : -- keywords: +patch pull_requests: +20858 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21714 ___ Python tracker ___

[issue41463] Avoid duplicating jump information from opcode.py in compile.c

New submission from Mark Shannon : opcode.py declares which jumps are relative and which are absolute. We duplicate that information in compile.c We should generate lookup tables in opcodes.h and to repeating that information in compile.c -- messages: 374735 nosy: Mark.Shannon