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 Demur Rumed
Recipients Adrian Wielgosik, Demur Rumed, mark.dickinson, serhiy.storchaka, vstinner
Date 2016-05-24.23:44:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464133455.46.0.788626211033.issue27097@psf.upfronthosting.co.za>
In-reply-to
Content
There's some difficulty in changing next_instr to an unsigned short* unless pointer arithmetic converts it back to unsigned char*. Code relies on f_lasti to be a byte index more than it relies on f_lasti to be -1 at first. Should this change include converting jump offsets to word increments? This patch seeks to be a minimal change to achieve the desired aligned/batched memory read behavior of NEXTOP/NEXTARG. Perhaps a clear description of how deep the changes should be is in order

It's also a bit hard to assert pointer alignment without failling back to stdint's uintptr_t. It may be sufficient to assert f_lasti is an even number
History
Date User Action Args
2016-05-24 23:44:15Demur Rumedsetrecipients: + Demur Rumed, mark.dickinson, vstinner, serhiy.storchaka, Adrian Wielgosik
2016-05-24 23:44:15Demur Rumedsetmessageid: <1464133455.46.0.788626211033.issue27097@psf.upfronthosting.co.za>
2016-05-24 23:44:15Demur Rumedlinkissue27097 messages
2016-05-24 23:44:15Demur Rumedcreate