On Tue, Nov 10, 2015 at 05:22:40PM +0100, Christophe Lyon wrote:
> On 10 November 2015 at 12:41, Robert Suchanek
> <robert.sucha...@imgtec.com> wrote:
> > Hi Christophe,
> >
> >> Hi,
> >>
> >> Since you committed this (r230087 if I'm correct), I can see that GCC
> >> fails to build
> >> ligfortran for target arm-none-linuxgnueabi --with-cpu=cortex-a9.
> > ...
> >>
> >> Can you have a look?
> >
> > Sorry for the breakage. I see that my assertion is being triggered.
> > I'll investigate this and check whether the assertion is correct or
> > something else needs to be done.
> >
>
> Now that 'make check' has had enough time to run, I can see several
> regressions in the configurations where GCC still builds.
> For more details:
> http://people.linaro.org/~christophe.lyon/cross-validation/gcc/trunk/230087/report-build-info.html
>
This also causes failures for AArch64 -mcpu=cortex-a57 targets. This
testcase:
void
foo (unsigned char *out, const unsigned char *in, int a)
{
for (int i = 0; i < a; i++)
{
out[0] = in[2];
out[1] = in[1];
out[2] = in[0];
in += 3;
out += 3;
}
}
Fails as so:
foo.c: In function 'void foo(unsigned char*, const unsigned char*, int)':
foo.c:12:1: internal compiler error: in scan_rtx_reg, at regrename.c:1074
}
^
0xbe00f8 scan_rtx_reg
..../gcc/regrename.c:1073
0xbe0ad5 scan_rtx
..../gcc/regrename.c:1401
0xbe1038 record_out_operands
..../gcc/regrename.c:1554
0xbe1f50 build_def_use
..../gcc/regrename.c:1802
0xbe1f50 regrename_analyze(bitmap_head*)
..../gcc/regrename.c:726
0xf7a0c7 func_fma_steering::execute_fma_steering()
..../gcc/config/aarch64/cortex-a57-fma-steering.c:1026
0xf7a9c1 pass_fma_steering::execute(function*)
..../gcc/config/aarch64/cortex-a57-fma-steering.c:1063
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
When compiled with:
<gcc-aarch64> -O3 -mcpu=cortex-a57 foo.c
Thanks,
James
