[Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Sat Jan 8 23:26:03 CET 2011
- Previous message: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
- Next message: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, 8 Jan 2011 22:58:51 +0100 Stefan Krah <stefan at bytereef.org> wrote:
Antoine Pitrou <solipsis at pitrou.net> wrote: > On Sat, 8 Jan 2011 12:03:35 -0800 (PST) > "Ralf W. Grosse-Kunstleve" <rwgk at yahoo.com> wrote: > > I just wanted to share an observation in case Python developers are > > interested: > > Python 2.7.1 doesn't build with the current gcc 4.6 svn. > > Note that gcc 4.6 is now in "bug-fix only" mode. > > You should report a bug with the gcc developers. > By the way, can you try to build Python 3.2 too?
I can reproduce this with release27-maint on Fedora-14/amd64/gcc-4.6. -fno-strict-aliasing is enabled.
It might be interesting to have a buildbot with a bleeding edge toolchain. Although in this case nobody rushed to diagnose the three-month old issue anyway:
There is an issue for this:
Regards
Antoine.
- Previous message: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
- Next message: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]