From: Bernardo Innocenti <bernie@develer.com>
To: GCC Mailing List <gcc@gcc.gnu.org>
Cc: Gunther Nikl <gni@gecko.de>, Richard Zidlicky <rz@linux-m68k.org>,
Jim Wilson <wilson@specifixinc.com>
Subject: m68k-linux regressions
Date: Sat, 20 Mar 2004 06:48:00 -0000 [thread overview]
Message-ID: <405BBE7B.4000904@develer.com> (raw)
Hello,
I've finally finished running the C and C++ test suites on
the m68k-linux box kindly offered by the Debian people.
I've posted the results here:
http://gcc.gnu.org/ml/gcc-testresults/2004-03/msg01015.html
The number of failures might look high, but it's much better
than I what I got from my previous tests in January (>170
failures on m68k-netbsd!).
We also have recent testresults for m68k-linux with 3.3.3:
http://gcc.gnu.org/ml/gcc-testresults/2004-03/msg00530.html
Diffing the gcc.dg parts of the summaries I get this:
--- klose-3.4-20040310.test_summary 2004-03-20 04:40:17.353990030 +0100
+++ tky-3.4-20040320-test_summary 2004-03-20 04:36:20.821450732 +0100
@@ -1,33 +1,51 @@
=== gcc tests ===
Running target unix
WARNING: program timed out.
-FAIL: gcc.c-torture/compile/20001226-1.c, -O1
-WARNING: program timed out.
-FAIL: gcc.c-torture/compile/20001226-1.c, -O2
+FAIL: gcc.c-torture/compile/20001226-1.c (test for excess errors)
WARNING: program timed out.
-FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -fomit-frame-pointer
+FAIL: gcc.c-torture/compile/20001226-1.c (test for excess errors)
WARNING: program timed out.
-FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -g
+FAIL: gcc.c-torture/compile/20001226-1.c (test for excess errors)
WARNING: program timed out.
-FAIL: gcc.c-torture/compile/20001226-1.c, -Os
+FAIL: gcc.c-torture/compile/20001226-1.c (test for excess errors)
+FAIL: gcc.c-torture/compile/921118-1.c (test for excess errors)
+FAIL: gcc.c-torture/compile/921118-1.c (test for excess errors)
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -O1
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -O2
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -O3 -fomit-frame-pointer
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -O3 -g
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -Os
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -O1
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -O2
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -O3 -fomit-frame-pointer
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -O3 -g
+FAIL: gcc.c-torture/execute/builtins/string-3.c execution, -Os
+FAIL: gcc.c-torture/execute/20001108-1.c execution, -O3 -fomit-frame-pointer
+FAIL: gcc.c-torture/execute/20001108-1.c execution, -O3 -g
+FAIL: gcc.c-torture/execute/20001203-2.c execution, -O3 -fomit-frame-pointer
+FAIL: gcc.c-torture/execute/20001203-2.c execution, -O3 -g
+FAIL: gcc.c-torture/execute/20020418-1.c execution, -O1
FAIL: gcc.c-torture/execute/20020418-1.c execution, -O2
FAIL: gcc.c-torture/execute/20020418-1.c execution, -Os
+FAIL: gcc.c-torture/execute/20020720-1.c compilation, -O1
+UNRESOLVED: gcc.c-torture/execute/20020720-1.c execution, -O1
+FAIL: gcc.c-torture/execute/930921-1.c execution, -O3 -fomit-frame-pointer -funroll-loops
+FAIL: gcc.c-torture/execute/930921-1.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
+FAIL: gcc.c-torture/execute/950511-1.c compilation, -O3 -fomit-frame-pointer
+UNRESOLVED: gcc.c-torture/execute/950511-1.c execution, -O3 -fomit-frame-pointer
+FAIL: gcc.c-torture/execute/950511-1.c compilation, -O3 -g
+UNRESOLVED: gcc.c-torture/execute/950511-1.c execution, -O3 -g
+FAIL: gcc.c-torture/execute/960416-1.c compilation, -O3 -fomit-frame-pointer
+UNRESOLVED: gcc.c-torture/execute/960416-1.c execution, -O3 -fomit-frame-pointer
+FAIL: gcc.c-torture/execute/960416-1.c compilation, -O3 -g
+UNRESOLVED: gcc.c-torture/execute/960416-1.c execution, -O3 -g
+FAIL: gcc.c-torture/execute/961213-1.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O0
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O1
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2
@@ -44,148 +62,155 @@
FAIL: gcc.c-torture/execute/loop-2g.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/loop-2g.c execution, -O3 -g
FAIL: gcc.c-torture/execute/loop-2g.c execution, -Os
-FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O0
-FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O1
-FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O2
-FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O3 -fomit-frame-pointer
-FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O3 -g
-FAIL: gcc.c-torture/execute/string-opt-10.c execution, -Os
-FAIL: gcc.c-torture/execute/string-opt-17.c execution, -O1
-FAIL: gcc.c-torture/execute/string-opt-17.c execution, -O2
-FAIL: gcc.c-torture/execute/string-opt-17.c execution, -O3 -fomit-frame-pointer
-FAIL: gcc.c-torture/execute/string-opt-17.c execution, -O3 -g
-FAIL: gcc.c-torture/execute/string-opt-17.c execution, -Os
-FAIL: gcc.c-torture/execute/string-opt-9.c execution, -O0
-FAIL: gcc.c-torture/execute/string-opt-9.c execution, -O1
-FAIL: gcc.c-torture/execute/string-opt-9.c execution, -O2
-FAIL: gcc.c-torture/execute/string-opt-9.c execution, -O3 -fomit-frame-pointer
-FAIL: gcc.c-torture/execute/string-opt-9.c execution, -O3 -g
-FAIL: gcc.c-torture/execute/string-opt-9.c execution, -Os
-FAIL: gcc.dg/20020312-2.c (test for excess errors)
-WARNING: gcc.dg/20020312-2.c compilation failed to produce executable
+WARNING: program timed out.
+FAIL: gcc.c-torture/execute/memcpy-bi.c compilation, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
+UNRESOLVED: gcc.c-torture/execute/memcpy-bi.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
+WARNING: program timed out.
+FAIL: gcc.dg/20020425-1.c (test for excess errors)
FAIL: gcc.dg/bitfld-3.c execution test
FAIL: gcc.dg/bitfld-4.c execution test
XPASS: gcc.dg/c99-flex-array-4.c sizeof != offsetof (test for bogus messages, line 24)
-FAIL: gcc.dg/duff-2.c (test for excess errors)
FAIL: gcc.dg/pack-test-1.c (test for excess errors)
-FAIL: gcc.dg/uninit-A.c uninitialized variable warning (test for bogus messages, line 52)
-FAIL: gcc.dg/uninit-A.c uninitialized variable warning (test for bogus messages, line 53)
+XPASS: gcc.dg/sibcall-3.c execution test
+XPASS: gcc.dg/sibcall-4.c execution test
FAIL: gcc.dg/weak/typeof-2.c scan-assembler baz3.*baz3.*baz3.*baz3.*baz3.*baz3
=== gcc Summary ===
-# of expected passes 20999
-# of unexpected failures 48
-# of unexpected successes 1
-# of expected failures 68
-# of unsupported tests 194
-/build/buildd/gcc-3.3-3.3.3ds5/build/gcc/xgcc version 3.3.3 (Debian 20040306)
+# of expected passes 24770
+# of unexpected failures 53
+# of unexpected successes 3
+# of expected failures 67
+# of unresolved testcases 6
+# of untested testcases 7
+# of unsupported tests 318
+/home/bernie/src/gcc/m68k-linux-3.4-build/gcc/xgcc version 3.4.0 20040313 (prerelease)
-Compiler version: 3.3.3 (Debian 20040306)
+Compiler version: 3.4.0 20040313 (prerelease)
Platform: m68k-unknown-linux-gnu
-configure flags: --host=m68k-linux -v --enable-languages=c,c++,java,f77,pascal,objc,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-sjlj-exceptions --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc
-BOOT_CFLAGS=-g -O2
+configure flags: --prefix=/home/bernie/src/m68k-linux-3.4-install --enable-languages=c,c++ --with-gnu-ld --with-gnu-as --disable-nls
+
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next reply other threads:[~2004-03-20 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 6:48 Bernardo Innocenti [this message]
2004-03-22 1:27 ` Richard Zidlicky
2004-03-22 4:30 ` Bernardo Innocenti
2004-03-22 7:48 ` Bernardo Innocenti
2004-03-25 23:25 ` Jim Wilson
2004-03-22 5:16 ` Matthias Klose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=405BBE7B.4000904@develer.com \
--to=bernie@develer.com \
--cc=gcc@gcc.gnu.org \
--cc=gni@gecko.de \
--cc=rz@linux-m68k.org \
--cc=wilson@specifixinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).