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 lemburg
Recipients jyasskin, lemburg, loewis, pitrou
Date 2010-07-08.22:09:52
SpamBayes Score 0.0028600127
Marked as misclassified No
Message-id <>
In-reply-to <1278624522.3235.38.camel@localhost.localdomain>
Antoine Pitrou wrote:
> Antoine Pitrou <> added the comment:
>> gcc 4.4.2 on AMD processors ...
> So? Compilers have all kinds of optimization bugs, it's not our job to
> have a compiler matrix with optimal flags per compiler.

No, but we do need to make sure that the casual user does not
run into such issues by using the default compiler on a typical
Unix system with Python default settings.

An expert user can always use the right compiler... but then an
expert can also use the configure option :-)

gcc 4.4.2 is not exactly an old version of gcc. The perspective
of (apparently) not having the patch in in Ubuntu 10.4 LTS's
default compiler suggests that we do need be more careful about
enabling the switch per default.

> (well, you can of course maintain such a matrix if you want)
> For the record, I had an Athlon 64 machine until very recently, used it
> with gcc 4.4.x and computed gotos were better than without.

Perhaps someone can report whether this affects Ubuntu 10.4 LTS ?!
Date User Action Args
2010-07-08 22:10:05lemburgsetrecipients: + lemburg, loewis, pitrou, jyasskin
2010-07-08 22:09:52lemburglinkissue9203 messages
2010-07-08 22:09:52lemburgcreate