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 ajaksu2, alexandre.vassalotti, bboissin, blaisorblade, christian.heimes, collinwinter, djc, facundobatista, gregory.p.smith, jyasskin, lemburg, pitrou, ralph.corderoy, rhettinger, skip.montanaro, theatrus
Date 2009-01-10.11:29:34
SpamBayes Score 0.407346
Marked as misclassified No
Message-id <>
In-reply-to <1231581315.7676.14.camel@localhost>
On 2009-01-10 10:55, Antoine Pitrou wrote:
> Antoine Pitrou <> added the comment:
>> It looks like we still didn't manage, and since ICC is the best 
>> compiler out there, this matters.
> Well, from the perspective of Python, what matters mostly is the
> commonly used compilers (that is, gcc and MSVC). I doubt many people
> compile Python with icc, honestly.

Agreed. Our main targets should be GCC for Linux and MSVC for Windows.

On other platforms such as Solaris and AIX, the native vendor compilers
are commonly used for compiling Python.

That said, with a configure option to turn the optimization on and
off, there shouldn't be any problem with slowdowns.

> Same for CPU-specific tuning: I don't think we want to ship Python with
> compiler flags which depend on the particular CPU being used.

Certainly not in the binaries we release on

Of course, people are still free to setup OPT to have the compiler
generate CPU specific code.
Date User Action Args
2009-01-10 11:29:52lemburgsetrecipients: + lemburg, skip.montanaro, collinwinter, rhettinger, facundobatista, gregory.p.smith, pitrou, christian.heimes, ajaksu2, alexandre.vassalotti, jyasskin, djc, ralph.corderoy, bboissin, blaisorblade, theatrus
2009-01-10 11:29:36lemburglinkissue4753 messages
2009-01-10 11:29:34lemburgcreate