[Python-Dev] Python 3 optimizations, continued, continued again...

Georg Brandl g.brandl at gmx.net
Tue Jan 31 21:50:57 CET 2012

Am 31.01.2012 16:46, schrieb stefan brunthaler:
>> If I read the patch correctly, most of it is auto-generated (and there
>> is probably a few spurious changes that blow it up, such as the
>> python-gdb.py file).
> Hm, honestly I don't know where the python-gdb.py file comes from, I
> thought it came with the switch from 3.1 to the tip version I was
> using. Anyways, I did not tuch it or at least have no recollection of
> doing so. Regarding the spurious changes: This might very well be,
> regression testing works, and it would actually be fairly easy to
> figure out crashes (e.g., by tracing all executed bytecode
> instructions and seeing if all of them are actually executed, I could
> easily do that if wanted/necessary.)

There is also the issue of the two test modules removed from the
test suite.

>> But the tool that actually generates the code
>> doesn't seem to be included?  (Which means that in this form, the
>> patch couldn't possibly be accepted.)
> Well, the tool is not included because it does a lot more (e.g.,
> generate the code for elimination of reference count operations.)
> Unfortunately, my interpreter architecture that achieves the highest
> speedups is more complicated, and I got the feeling that this is not
> going well with python-dev. So, I had the idea of basically using just
> one (but a major one) optimization technique and going with that. I
> don't see why you would need my code generator, though. Not that I
> cared, but I would need to strip down and remove many parts of it and
> also make it more accessible to other people. However, if python-dev
> decides that it wants to include the optimizations and requires the
> code generator, I'll happily chip in the extra work an give you the
> corresponding code generator, too.

Well, nobody wants to review generated code.


More information about the Python-Dev mailing list