➜

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 pitrou
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.09:54:59
SpamBayes Score 0.2838884
Marked as misclassified No
Message-id <1231581315.7676.14.camel@localhost>
In-reply-to <1231577551.9.0.477655297426.issue4753@psf.upfronthosting.co.za>
Content 
> 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.

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.
History
Date User Action Args
2009-01-10 09:55:00pitrousetrecipients: + pitrou, lemburg, skip.montanaro, collinwinter, rhettinger, facundobatista, gregory.p.smith, christian.heimes, ajaksu2, alexandre.vassalotti, jyasskin, djc, ralph.corderoy, bboissin, blaisorblade, theatrus
2009-01-10 09:54:59pitroulinkissue4753 messages
2009-01-10 09:54:59pitroucreate