GCC-30-CVS Embedded Cross Status Spreadsheet

[Joel Sherrill <joel dot sherrill at OARcorp dot com>]

I have compiled a GNUmeric spreadsheet showing the basic
status of each of the cross configuration I have tried
to build.  It is attached along with a PostScript 
output for those who don't have GNUmeric.

I don't know if this is useful or not or presented in 
the best form. 

Configuration Information: 
  Host     --> GNU/Linux RedHat 6.2
  GCC      --> GCC-30-CVS from July 23.
  Binutils --> 2.11.2 with minor patches
  Newlib   --> 1.9.0 with minor patches

  Targets  -->
    a29k-coff arc-elf arm-elf h8300-coff hppa1.1-proelf i386-elf
    i960-coff i960-elf m68k-coff m68k-elf mips-elf
    mips64orion-elf powerpc-elf sh-coff sh-elf sparc-elf v850-elf
    fr30-elf m32r-elf mcore-elf mn10200-elf mn10300-elf avr-elf
    d10v-elf d30v-elf

  Configuration command:
    ../gcc-30cvs/configure --target=XXX --prefix=/opt/gnucross \
       --with-gnu-as --with-gnu-ld --with-newlib --verbose \
       '--enable-languages=c,c++'
    NOTE: I have done with with various language options to
          get results.

The basic notation on the spreadsheet is:

failed  - indicated gdb or binutils did not build for target
NA      - target or feature not supported
unbuilt - earlier failures prevented building this.  I really
          have not tried to build much beyond C/C++.  If 
          C++ failed to build, I have went back and built C only.
report  - test report filed on indicated date.
PRxxxx  - GNATS PR for the problem that stopped the build

No PRs are included for test suite failures.  I have not really
analyzed the test results.  This is a good place for someone to
help and I posted earlier begging on this one. See 
http://gcc.gnu.org/ml/gcc/2001-07/msg01790.html for details.

NOTE: I am doing this as a volunteer and really can't invest
enormous amounts of time in analyzing test results or debugging
20+ targets.  I am already ignoring real bill-paying work to 
do this. I am happy to repeat test runs if someone provides
a patch, help analyze something, or even help someone duplicate
the test setup. I am just a messenger/tester here and really
am in no position to fix all these problems. :)


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985

cross_results.gnumeric

output.ps