Marc-Andre Lemburg <m...@egenix.com> added the comment: On 2009-01-10 10:55, Antoine Pitrou wrote: > Antoine Pitrou <pit...@free.fr> 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 python.org. Of course, people are still free to setup OPT to have the compiler generate CPU specific code. _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4753> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
