[Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0 (original) (raw)
Jesus Cea jcea at jcea.es
Wed May 12 15:56:48 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 ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/05/10 15:32, Nick Coghlan wrote:
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?
When I do a "python setup.py install", the options used to compile the module are the same that used to compile python itself.
Jesus Cea Avion // /// /// jcea at jcea.es - http://www.jcea.es/ // // // // // jabber / xmpp:jcea at jabber.org // // ///// . // // // // // "Things are not so easy" // // // // // // "My name is Dump, Core Dump" /// //_/ // // "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBS+qzn5lgi5GaxT1NAQJ5BgQAimvcMssT57iuuLpaI9P9GXKGZf9VUAzj F4XJM/lT4Qtzu22jecIvEej0MyiMR/4qHvns8lgqLXn/30pkYrkmYcjxFigpM7Bl rOKMYeAr3ki8dN87APkoiMKOJHByXlEUZu+BowCOXcUCtGYcENLwQ+STr1NyCsUB IINfh1pJ2Nc= =GiUG -----END PGP SIGNATURE-----
- 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 ]