This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author iritkatriel
Recipients iritkatriel
Date 2022-02-20.14:48:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645368528.16.0.363497063609.issue46808@roundup.psfhosted.org>
In-reply-to
Content
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).
History
Date User Action Args
2022-02-20 14:48:48iritkatrielsetrecipients: + iritkatriel
2022-02-20 14:48:48iritkatrielsetmessageid: <1645368528.16.0.363497063609.issue46808@roundup.psfhosted.org>
2022-02-20 14:48:48iritkatriellinkissue46808 messages
2022-02-20 14:48:48iritkatrielcreate