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 pitrou
Recipients pitrou, serprex
Date 2010-07-12.11:33:16
SpamBayes Score 0.0019847527
Marked as misclassified No
Message-id <1278934397.98.0.415174037339.issue9225@psf.upfronthosting.co.za>
In-reply-to
Content
> Oddly, at least with pybench, use of PREDICT(BINARY_SUBSCR) in
> DUP_TOP_TWO seems to show an always right PREDICT as slower than
> FAST_DISPATCH

The main point of computed gotos is to allow the CPU's branch predictor to predict opcode pairs by itself. So, yes, adding a manual PREDICT() might actually slow down the code (probably depending on the CPU model).

By the way, when you modify the bytecode, you have to change the magic number in Python/import.c.
History
Date User Action Args
2010-07-12 11:33:18pitrousetrecipients: + pitrou, serprex
2010-07-12 11:33:17pitrousetmessageid: <1278934397.98.0.415174037339.issue9225@psf.upfronthosting.co.za>
2010-07-12 11:33:16pitroulinkissue9225 messages
2010-07-12 11:33:16pitroucreate