Joern RENNECKE <[EMAIL PROTECTED]> wrote:
> My simulator now segfaults for every single execution test built with
> mainline; when I try gdb, it also segfaults,
> somewhere in the dwarf handling code.
> Unless someone comes up with a viable concept how to maintain sh64
> support in gcc, I think we have to deprecate
> it now, since at the time of the gcc 4.3 release it can be expected to
> have bitrotted too much to be more useful than
> or even as useful as a vintage release.
I agree with Joern about the disastrous status of the simulator
test, though not every execution tests fail in my environment:
=== g++ Summary ===
# of expected passes 12270
# of unexpected failures 235
# of unexpected successes 1
# of expected failures 65
# of unresolved testcases 50
# of unsupported tests 140
=== gcc Summary ===
# of expected passes 38606
# of unexpected failures 610
# of unexpected successes 2
# of expected failures 73
# of unresolved testcases 42
# of untested testcases 28
# of unsupported tests 413
=== libstdc++ Summary ===
# of expected passes 2390
# of unexpected failures 491
# of unexpected successes 1
# of expected failures 10
# of unsupported tests 153
Compiler version: 4.2.0 20060823 (experimental)
Platform: sh64-unknown-elf
configure flags: --host=i686-pc-linux-gnu --target=sh64-unknown-elf
--with-ld=/usr/local/bin/sh64-unknown-elf-ld
--with-as=/usr/local/bin/sh64-unknown-elf-as --disable-libssp --with-headers
--with-newlib --disable-gdb --enable-languages=c,c++
Perhaps it's because I gave up the unified tree and use older sim
and binutils.
Oddly the result of the regtest on sh64-unknown-linux-gnu looks not
so broken:
http://gcc.gnu.org/ml/gcc-testresults/2006-08/msg01073.html
Regards,
kaz
