Antoine Pitrou wrote: > Or you could submit patches piecewise on http://bugs.python.org > I think the first step would be to switch to 16-bit bytecodes. It would be > uncontroversial (the increase in code size probably has no negative effect) > and > would provide the foundation for all of your optimizations.
I wouldn't consider changing from bytecode to wordcode uncontroversial - the potential to have an effect on cache hit ratios means it needs to be benchmarked (the U-S performance tests should be helpful there). It's the same basic problem where any changes to the ceval loop can have surprising performance effects due to the way they affect the compiled switch statements ability to fit into the cache and other low level processor weirdness. If there was an old style map of the CPython code base, the whole area would have "'ware, here be dragons" written over the top of it ;) Cheers, Nick. P.S. Note that I'm not saying I'm fundamentally opposed to a change to wordcode - just that it needs to be benchmarked fairly thoroughly first. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
