[issue46808] remove NEXT_BLOCK() from compile.c

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

[issue46808] remove NEXT_BLOCK() from compile.c

Change by Brandt Bucher : -- nosy: +brandtbucher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46808] remove NEXT_BLOCK() from compile.c

Mark Shannon added the comment: New changeset c579243eb62d3182c84004cd72dcf6ef59100643 by Irit Katriel in branch 'main': bpo-46808: remove NEXT_BLOCK() from compile.c (GH-31448) https://github.com/python/cpython/commit/c579243eb62d3182c84004cd72dcf6ef59100643 -- nosy: +Mark.Shannon

[issue46808] remove NEXT_BLOCK() from compile.c

Irit Katriel added the comment: The patch in PR31448 delays the creation of an implicit block to when it is needed (do if we begin using another block before a new instruction is added, the implicit block is never created). I counted how many empty blocks are being detected by the

[issue46808] remove NEXT_BLOCK() from compile.c

Change by Irit Katriel : -- keywords: +patch pull_requests: +29576 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31448 ___ Python tracker ___

[issue46808] remove NEXT_BLOCK() from compile.c

New submission from Irit Katriel : 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