[Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0 (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Wed May 12 15:32:55 CEST 2010
- Previous message: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0
- Next message: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jesus Cea wrote:
Proposal: add "-fno-tree-vectorize" to compilation options for 2.7/3.2.
Will this actually help? Won't there still be a problem if any extension module is compiled with GCC 4.5.0 without that option, regardless of the options used to build Python itself?
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0
- Next message: [Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]