This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Known gcc testsuite issues (was: gcc-3.3, host==x86, target==ppc7450)
- From: Dan Kegel <dank at kegel dot com>
- To: mike at whitehillfarm dot com
- Cc: crossgcc at sources dot redhat dot com, GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Thu, 28 Aug 2003 11:11:16 -0700
- Subject: Known gcc testsuite issues (was: gcc-3.3, host==x86, target==ppc7450)
- References: <3F4E2905.90903@skycomputers.com>
Michael LeBlanc wrote:
With a lot of help from Dan Kegel, I built and tested the toolchain,
host x86-Redhat-9, target ppc7450-YellowDogLinux-2.3.
And thanks to Michael, crosstool-howto.html now has a better
discussion of how to avoid rsh protocol errors when running the remote
regression tests.
> The results are below.
I'll intersperse links to the gcc bugzilla after each FAIL in Michael's
results. All but one of them appear to be testsuite problems.
> === gcc tests ===
>
FAIL: gcc.dg/20020103-1.c scan-assembler-not LC
http://gcc.gnu.org/PR11594
FAIL: gcc.dg/duff-2.c (test for excess errors)
http://gcc.gnu.org/PR11592
FAIL: gcc.dg/format/ext-1.c printf_unlocked (test for warnings, line 125)
...
FAIL: gcc.dg/format/ext-3.c (test for excess errors)
http://gcc.gnu.org/PR12096
FAIL: gcc.misc-tests/bprob-1.c execution: file bprob-1.da does not exist
...
UNRESOLVED: gcc.misc-tests/bprob-2.c execution
http://gcc.gnu.org/PR12055
=== g++ tests ===
...
FAIL: g++.dg/bprob/g++-bprob-1.C execution: file g++-bprob-1.da does not exist
...
UNRESOLVED: g++.dg/bprob/g++-bprob-1.C execution
http://gcc.gnu.org/PR12055
FAIL: g++.dg/abi/mangle17.C (test for excess errors)
http://gcc.gnu.org/PR12097
=== libstdc++-v3 tests ===
...
FAIL: 27_io/filebuf_members.cc execution test
FAIL: 27_io/filebuf_virtuals.cc execution test
FAIL: 27_io/ifstream_members.cc execution test
FAIL: 27_io/istream_extractor_other.cc execution test
FAIL: 27_io/istream_seeks.cc execution test
FAIL: 27_io/istream_unformatted.cc execution test
FAIL: 27_io/ostream_inserter_other.cc execution test
http://gcc.gnu.org/PR11610
And that's it! I think none of those PRs are serious.
Only one I'm unsure about is PR11594.
The rest are simply problems in the testcases.
Your compiler looks clean. Congratulations!
- Dan
Compiler version: 3.3
Platform: powerpc-7450-linux-gnu
configure flags:
--target=powerpc-7450-linux-gnu
--host=i686-host_pc-linux-gnu
--with-cpu=7450
--enable-altivec
--disable-nls
--enable-threads=posix
--enable-symvers=gnu
--enable-__cxa_atexit
--enable-languages=c,c++
--enable-shared
--enable-c99
--enable-long-long
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045