* m68k-linux regressions
@ 2004-03-20 6:48 Bernardo Innocenti
2004-03-22 1:27 ` Richard Zidlicky
0 siblings, 1 reply; 6+ messages in thread
From: Bernardo Innocenti @ 2004-03-20 6:48 UTC (permalink / raw)
To: GCC Mailing List; +Cc: Gunther Nikl, Richard Zidlicky, Jim Wilson
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/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: m68k-linux regressions
2004-03-20 6:48 m68k-linux regressions Bernardo Innocenti
@ 2004-03-22 1:27 ` Richard Zidlicky
2004-03-22 4:30 ` Bernardo Innocenti
2004-03-22 5:16 ` Matthias Klose
0 siblings, 2 replies; 6+ messages in thread
From: Richard Zidlicky @ 2004-03-22 1:27 UTC (permalink / raw)
To: Bernardo Innocenti; +Cc: GCC Mailing List, Gunther Nikl, Jim Wilson
On Sat, Mar 20, 2004 at 04:46:03AM +0100, Bernardo Innocenti wrote:
> 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!).
lot of the failures may not be failures, too small timeout for
m68k.
> --enable-__cxa_atexit --enable-sjlj-exceptions --enable-clocale=gnu
why sjlj exceptions? Is something terribly broken with the other
exception model?
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: m68k-linux regressions
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
1 sibling, 2 replies; 6+ messages in thread
From: Bernardo Innocenti @ 2004-03-22 4:30 UTC (permalink / raw)
To: Richard Zidlicky; +Cc: GCC Mailing List, Gunther Nikl, Jim Wilson
Richard Zidlicky wrote:
>>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!).
>
> lot of the failures may not be failures, too small timeout for
> m68k.
Where do I change Dejagnu's default timeout for the gcc.dg
testsuite?
>>--enable-__cxa_atexit --enable-sjlj-exceptions --enable-clocale=gnu
>
> why sjlj exceptions? Is something terribly broken with the other
> exception model?
I've copied that from the configuation of the system compiler of
the m68k host. It runs Debian unstable:
Reading specs from /usr/lib/gcc-lib/m68k-linux/3.3.3/specs
Configured with: ../src/configure -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 m68k-linux
Thread model: posix
gcc version 3.3.3 (Debian 20040306)
I'll re-run the tests with DWARF2 exceptions enabled, it would be useful
as a confidence test to debug exceptions on m68k-uclinux, which are still
buggy on the ColdFire.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: m68k-linux regressions
2004-03-22 1:27 ` Richard Zidlicky
2004-03-22 4:30 ` Bernardo Innocenti
@ 2004-03-22 5:16 ` Matthias Klose
1 sibling, 0 replies; 6+ messages in thread
From: Matthias Klose @ 2004-03-22 5:16 UTC (permalink / raw)
To: Richard Zidlicky
Cc: Bernardo Innocenti, GCC Mailing List, Gunther Nikl, Jim Wilson
Richard Zidlicky writes:
> On Sat, Mar 20, 2004 at 04:46:03AM +0100, Bernardo Innocenti wrote:
> lot of the failures may not be failures, too small timeout for
> m68k.
>
> > --enable-__cxa_atexit --enable-sjlj-exceptions --enable-clocale=gnu
>
> why sjlj exceptions? Is something terribly broken with the other
> exception model?
To be compatible with gcc-3.2, another ABI transition would have
delayed the Debian release process even more ...
Matthias
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: m68k-linux regressions
2004-03-22 4:30 ` Bernardo Innocenti
@ 2004-03-22 7:48 ` Bernardo Innocenti
2004-03-25 23:25 ` Jim Wilson
1 sibling, 0 replies; 6+ messages in thread
From: Bernardo Innocenti @ 2004-03-22 7:48 UTC (permalink / raw)
To: Bernardo Innocenti
Cc: Richard Zidlicky, GCC Mailing List, Gunther Nikl, Jim Wilson
Bernardo Innocenti wrote:
>>> --enable-__cxa_atexit --enable-sjlj-exceptions --enable-clocale=gnu
>>
>> why sjlj exceptions? Is something terribly broken with the other
>> exception model?
>
> I've copied that from the configuation of the system compiler of
> the m68k host. It runs Debian unstable:
Correction: the version of GCC used for the test was _not_ using
sjlj exceptions. The line you're quoting comes from the
3.3.3 test results done by Matthias Klose.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: m68k-linux regressions
2004-03-22 4:30 ` Bernardo Innocenti
2004-03-22 7:48 ` Bernardo Innocenti
@ 2004-03-25 23:25 ` Jim Wilson
1 sibling, 0 replies; 6+ messages in thread
From: Jim Wilson @ 2004-03-25 23:25 UTC (permalink / raw)
To: Bernardo Innocenti; +Cc: Richard Zidlicky, GCC Mailing List, Gunther Nikl
On Sun, 2004-03-21 at 13:41, Bernardo Innocenti wrote:
> Where do I change Dejagnu's default timeout for the gcc.dg
> testsuite?
There are some differences here depending on exactly how you are running
programs, e.g. by directly invoking them, by invoking gdb and running
them inside gdb, by using kermit to connect to a target, by running them
under a simulator, etc.
For a native linux, you are probably running them directly, in which
case I think the default timeout comes from dejagnu/lib/remote.exp.
Search for "set timeout 300", which sets the default to 5 minutes. You
shouldn't actually modify this file though, You should write your own
target file, e.g. baseboards/m68k-linux.exp, and set timeout there to
override the default. You could start by just copying the unix.exp
file. You would then use --target_board=m68k-linux to run the tests.
If "set timeout" doesn't work, try "set_board_info gcc,timeout".
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-03-25 20:47 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-20 6:48 m68k-linux regressions Bernardo Innocenti
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
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).