[New-bugs-announce] [issue46808] remove NEXT_BLOCK() from compile.c

Irit Katriel report at bugs.python.org
Sun Feb 20 09:48:48 EST 2022


New submission from Irit Katriel <iritkatriel at gmail.com>:

The compiler currently requires the code-generation functions to explicitly specify where basic blocks end, with a NEXT_BLOCK().

If you get that wrong, you get an exception about "malformed control flow graph" later, in the cfg analysis stage. It is not obvious then where the error is, and it makes it difficult to make changes in the compiler. 

We can instead make the compiler implicitly create a new block when this is needed (which is after specific opcodes).

----------
assignee: iritkatriel
components: Interpreter Core
messages: 413589
nosy: iritkatriel
priority: normal
severity: normal
status: open
title: remove NEXT_BLOCK() from compile.c
type: enhancement
versions: Python 3.11

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue46808>
_______________________________________


More information about the New-bugs-announce mailing list