Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

2011-01-11 Thread Ralf W. Grosse-Kunstleve
> Does that version of gcc emit any warnings during compilation? Yes, there are a few: http://cci.lbl.gov/~rwgk/tmp/gcc_trunk_168695_fc14_py271/ This is with: g++ (GCC) 4.6.0 20110112 (experimental) Ralf___ Python-Dev mailing list Python-Dev@python.o

Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

2011-01-11 Thread Daniel Stutzbach
On Sat, Jan 8, 2011 at 12:03 PM, Ralf W. Grosse-Kunstleve wrote: > g++ (GCC) 4.6.0 20101206 (experimental) > % make > /bin/sh: line 1: 41686 Segmentation fault (core dumped) CC='gcc > -pthread' > LDSHARED='gcc -pthread -shared ' OPT='-DNDEBUG -g -fwrapv -O3 -Wall > -Wstrict-prototypes' ./pyth

Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

2011-01-08 Thread Stefan Krah
Antoine Pitrou wrote: > > 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:

Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

2011-01-08 Thread Antoine Pitrou
On Sat, 8 Jan 2011 22:58:51 +0100 Stefan Krah wrote: > Antoine Pitrou wrote: > > On Sat, 8 Jan 2011 12:03:35 -0800 (PST) > > "Ralf W. Grosse-Kunstleve" wrote: > > > I just wanted to share an observation in case Python developers are > > > interested: > > > Python 2.7.1 doesn't build with the cur

Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

2011-01-08 Thread Stefan Krah
Antoine Pitrou wrote: > On Sat, 8 Jan 2011 12:03:35 -0800 (PST) > "Ralf W. Grosse-Kunstleve" 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" m

Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

2011-01-08 Thread Martin v. Löwis
> BTW: I've been doing gcc pre-release testing regularly for many year, > starting > with gcc 3.3. This is the first time I see the Python build fail persistently > for several weeks. Wild guess: did configure detect that it needs to use -fno-strict-aliasing? Regards, Martin __

Re: [Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

2011-01-08 Thread Antoine Pitrou
On Sat, 8 Jan 2011 12:03:35 -0800 (PST) "Ralf W. Grosse-Kunstleve" 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

[Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

2011-01-08 Thread Ralf W. Grosse-Kunstleve
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. Some details: Fedora 14 64-bit. The first time I noticed the problem was in Nov or early Dec 2010; I'm pretty