Nick Coghlan <ncoghlan <at> gmail.com> writes: > > 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).
Well I said "/probably/ has no negative effect" :-) Actually, "wordcode" could allow accesses in the eval loop to be done on aligned words, so as to fetch operands in one step on little-endian CPUs (instead of recombining bytes manually). The change would be "uncontroversial", however, in that it wouldn't modify code complexity or increase the maintenance burden. Of course, performance checks have to be part of the review. > 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 ;) Just FYI: weakrefs and memoryviews are guarded by a mantichore, and only Benjamin can tame it. Regards Antoine. _______________________________________________ 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
