On 12 February 2013 15:38, Richard Biener <rguent...@suse.de> wrote:
> On Tue, 12 Feb 2013, Marcus Shawcroft wrote:
>
>> Sorry, I'll send that again copying gcc-patches in this time...
>>
>>
>> ---------- Forwarded message ----------
>> From: Marcus Shawcroft <marcus.shawcr...@gmail.com>
>> Date: 12 February 2013 15:17
>> Subject: Re: [PATCH] Fix PR56181, rewrite fix_loop_structure
>> To: Richard Biener <rguent...@suse.de>
>>
>>
>> On 12 February 2013 14:54, Richard Biener <rguent...@suse.de> wrote:
>>
>> > I can't reproduce this with a cross-compiler (--target=arm-non-eabi).
>> > How exactly did you configure?  Please provide -v output.
>> >
>> > Richard.
>>
>> I don't see the issue in arm-none-eabi either, just arm-none-linux-gnueabi.
>>
>>  --enable-shared --disable-libssp --disable-libmudflap
>> --with-plugin-ld=arm-none-linux-gnueabi-ld
>> --enable-languages=c,c++,fortran --with-arch=armv7-a
>> --with-fpu=vfpv3-d16 --with-float=softfp
>
> I still can't reproduce it.  I tried with pristine trunk rev. 195979.
>
> --target=arm-none-linux-gnueabi --enable-languages=c,c++,fortran
> --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp
>
> gcc> ./cc1 -quiet pr54458.c -O3 -fomit-frame-pointer -g  -I include
> gcc>
>
> Richard.

Richard, could you try that with -fPIC ?

cc1  -O3 -fPIC -fomit-frame-pointer -g -quiet pr54458.c
pr54458.c: In function ‘foo’:
pr54458.c:20:1: error: loop with header 9 not in loop tree
 }
 ^
pr54458.c:20:1: error: loop with header 33 not in loop tree
pr54458.c:20:1: error: loop with header 34 not in loop tree
pr54458.c:20:1: internal compiler error: in verify_loop_structure, at
cfgloop.c:1614
0x66c09c verify_loop_structure()
        /home/marcus/oban-work/work-trunk/src/gcc/gcc/cfgloop.c:1614
0x8f07fb unswitch_single_loop
        /home/marcus/oban-work/work-trunk/src/gcc/gcc/loop-unswitch.c:368
0x8eff2d unswitch_loops()
        /home/marcus/oban-work/work-trunk/src/gcc/gcc/loop-unswitch.c:147
0x8dd824 rtl_unswitch
        /home/marcus/oban-work/work-trunk/src/gcc/gcc/loop-init.c:441
Please submit a full bug report,


Cheers
/Marcus

Reply via email to