Message 413130 - Python tracker

➜

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	saulshanabrook
Recipients	JelleZijlstra, Mark.Shannon, saulshanabrook
Date	2022-02-12.13:56:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1644674216.71.0.455738351814.issue46724@roundup.psfhosted.org>
In-reply-to

Content
I added a patch to make `dis` work with the overflow format. I am looking into why the bytecode is emitted like this in the first place now. I see that currently, Python is trying to write a negative bytecode arg for the JUMP_ABSOLUTE and `instrsize` is saying this requires 4 args (which is not true, it only requires one). Is it intended behavior that the bytecode args will be negative? If so, then `instrsize` might have to be updated to handle this. It takes in an `unsigned int` but the oparg is actually a signed int.

I added a patch to make `dis` work with the overflow format.

I am looking into why the bytecode is emitted like this in the first place now. 

I see that currently, Python is trying to write a negative bytecode arg for the JUMP_ABSOLUTE and `instrsize` is saying this requires 4 args (which is not true, it only requires one). Is it intended behavior that the bytecode args will be negative? If so, then `instrsize` might have to be updated to handle this. It takes in an `unsigned int` but the oparg is actually a signed int.

History
Date	User	Action	Args
2022-02-12 13:56:57	saulshanabrook	set	recipients: + saulshanabrook, Mark.Shannon, JelleZijlstra
2022-02-12 13:56:56	saulshanabrook	set	messageid: <1644674216.71.0.455738351814.issue46724@roundup.psfhosted.org>
2022-02-12 13:56:56	saulshanabrook	link	issue46724 messages
2022-02-12 13:56:56	saulshanabrook	create