Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-May/100045.html below:

[Python-Dev] HEADS UP: Compilation risk with new GCC 4.5.0

• 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 ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4