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 jyasskin
Recipients ajaksu2, alexandre.vassalotti, bboissin, belopolsky, blaisorblade, christian.heimes, collinwinter, djc, facundobatista, gregory.p.smith, jyasskin, lemburg, pitrou, ralph.corderoy, rhettinger, skip.montanaro, spiv, theatrus
Date 2009-01-11.17:37:13
SpamBayes Score 0.0652206
Marked as misclassified No
Message-id <>
Here's a port of threadedceval5.patch to trunk. It passes the tests. I
haven't benchmarked this exact patch, but on one Intel Core2, a similar
patch got an 11%-14% speedup (on 2to3 and pybench).

I've also cleaned up Jakob Sievers' vmgen patch (representing
forth-style dispatch) a bit so that it passes all the tests, and on the
same machine it got a 13%-17% speedup. The vmgen patch is not quite at
feature parity (it throws out support for LLTRACE and a couple other
#defines), and there are fairly good arguments against committing it to
python at all (it requires installing and modifying vmgen to build), but
I'll post it after I've ported it to trunk.

Re skip and paolo: JITting and machine-specific assembly will probably
be important to speeding up Python in the long run, but they'll also
take a long while to get right, so we shouldn't let them distract us
from committing the dispatch optimization.
Date User Action Args
2009-01-11 17:37:25jyasskinsetrecipients: + jyasskin, lemburg, skip.montanaro, collinwinter, rhettinger, facundobatista, gregory.p.smith, spiv, belopolsky, pitrou, christian.heimes, ajaksu2, alexandre.vassalotti, djc, ralph.corderoy, bboissin, blaisorblade, theatrus
2009-01-11 17:37:23jyasskinsetmessageid: <>
2009-01-11 17:37:23jyasskinlinkissue4753 messages
2009-01-11 17:37:22jyasskincreate