[issue4128] Performance regression in long division in 2.6

Martin v. Löwis report at bugs.python.org
Fri Oct 17 16:09:07 CEST 2008

Martin v. Löwis <martin at v.loewis.de> added the comment:

The 2.5 build was done by VS 2003, with no PGO, and the 2.6 build was
done with VS 2008, and it used profile-guided optimization.

To understand why it behaves the way it behaves, you probably need to
look at the respective machine code.

I propose to close this as "won't fix"; I'm not interested in 150ms
speed differences when dividing 100000 digit numbers.

Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list