> -----Original Message-----
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of
> Ramana Radhakrishnan
> Sent: 08 April 2009 23:30
> To: Paolo Bonzini
> Cc: GCC Development; Ian Lance Taylor; Andreas Krebbel; Uros Bizjak
> Subject: Re: [cond-optab] svn branch created, looking for reviews for
> the "cleanup" parts
> 
> On Tue, Apr 7, 2009 at 11:03 AM, Ramana Radhakrishnan
> <raman...@gmail.com> wrote:
> >> To aid testing, I'd like people to help bootstrapping bootstrappable
> >> targets -- arm, alpha, ia64, pa, s390, x86_64.
> >
> > I'm bootstrapping the branch on an arm-linux-gnueabi target.
> 
> bootstrap on arm-linux-gnueabi completed. Regression testing C, C++
> now but the regression tests are still running. This is as of revision
> 145659 because the tester on the compile farm can be slightly slow.

I am seeing a few regressions with respect to trunk of a recent vintage.

The bulk of the failures hit the following ICE. 

/home/ramana/build-cond-optab/gcc/xgcc -B/home/ramana/build-cond-optab/gcc/
-O0  -w -c  -o pr37285.o
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/compile/pr37285.c
(timeout = \
300)
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/compile/pr37285.c: In
function '_bfd_xcoff_canonicalize_dynamic_reloc':^M
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/compile/pr37285.c:14:
error: unrecognizable insn:^M
(insn 26 25 27 9
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/compile/pr37285.c:5 (set
(reg:CC 24 cc)^M
        (compare:CC (plus:SI (reg:SI 0 r0)^M
                (const_int 1 [0x1]))^M
            (const_int 1 [0x1]))) -1 (nil))^M
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/compile/pr37285.c:14:
internal compiler error: in extract_insn, at recog.c:2074^M
Please submit a full bug report,^M
with preprocessed source if appropriate.^M
See <http://gcc.gnu.org/bugs.html> for instructions.^M
compiler exited with status 1

Here's a list of the tests that fail with this error message. Ofcourse you'd
count the execute tests as being twice which causes this to account for
about 28 failures + 3 compile failures = 31. The remainder are
limits-fncdef.c 

/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/compile/pr37285.c:14:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/compile/pr37285.c:14:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/compile/pr37285.c:14:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/930111-1.c:22:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/930111-1.c:22:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:
/home/ramana/cond-optab/gcc/testsuite/gcc.c-torture/execute/pr34154.c:8:
error: unrecognizable insn:

The other failures are with cc1 running out of VM which is a problem with
certain cases like limits*.c.


cheers
Ramana

---
Ramana Radhakrishnan
GNU Tools
ARM Ltd.



Reply via email to