On Tue, May 21, 2013 at 10:34:35AM +0200, Richard Biener wrote:
> On Mon, May 20, 2013 at 4:28 PM, Winfried Magerl
> wrote:
> > Hi,
> >
> > On Mon, May 20, 2013 at 09:40:52AM -0300, Adhemerval Zanella wrote:
> >> Hi,
> >>
> >> Thanks for reporting it, I saw it too when building glibc with gcc-trun
On Mon, May 20, 2013 at 4:28 PM, Winfried Magerl
wrote:
> Hi,
>
> On Mon, May 20, 2013 at 09:40:52AM -0300, Adhemerval Zanella wrote:
>> Hi,
>>
>> Thanks for reporting it, I saw it too when building glibc with gcc-trunk.
>> Carlos O'Donell already reported it could be an issue to glibc at
>> http:
Hi,
On Mon, May 20, 2013 at 09:40:52AM -0300, Adhemerval Zanella wrote:
> Hi,
>
> Thanks for reporting it, I saw it too when building glibc with gcc-trunk.
> Carlos O'Donell already reported it could be an issue to glibc at
> http://sourceware.org/ml/libc-alpha/2013-02/msg00299.html and I also no
Hi,
I've tried to compile upcoming glibc-2.18 with gcc-4.8.x and optimized
with '-O3' and testsuite breaks horrible with SIGSEGV and eating up
all available memory.
I've tracked it down to the flag 'tree-loop-distribute-patterns' and can
reproduce the problem with CFLAGS='-g -O2 -ftree-loop-distr
