public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23602] New: [4.1 regression] 1081 test failures in libjava, when configured for i486-linux
Date: Sun, 28 Aug 2005 16:41:00 -0000 [thread overview]
Message-ID: <20050828164012.23602.debian-gcc@lists.debian.org> (raw)
configuring HEAD 20050828 for i486-linux (instead of the default i686-linux),
libjava fails with 1081 test failures (instead of two with i686-linux).
apparently all the execution tests fail. I don't see any additional information
from the test log (attached). Compiling the a testcase by hand, and running it,
succeeds.
Environment is current Debian unstable, binutils 2.16.1, glibc-2.3.5.
Matthias
Running
/home/packages/gcc/snap/tst/gcc-20050828/libjava/testsuite/libjava.lang/lang.exp ...
FAIL: ArrayStore execution - source compiled test
FAIL: ArrayStore execution - gij test
FAIL: ArrayStore execution - bytecode->native test
FAIL: ArrayStore -O3 execution - source compiled test
FAIL: ArrayStore execution - gij test
FAIL: ArrayStore -O3 execution - bytecode->native test
FAIL: ArrayStore2 execution - source compiled test
FAIL: ArrayStore2 execution - gij test
FAIL: ArrayStore2 execution - bytecode->native test
FAIL: ArrayStore2 -O3 execution - source compiled test
FAIL: ArrayStore2 execution - gij test
FAIL: ArrayStore2 -O3 execution - bytecode->native test
[...]
FAIL: utilTest execution - source compiled test
FAIL: utilTest execution - gij test
FAIL: utilTest execution - bytecode->native test
FAIL: utilTest -O3 execution - source compiled test
FAIL: utilTest execution - gij test
FAIL: utilTest -O3 execution - bytecode->native test
FAIL: verify execution - source compiled test
FAIL: verify execution - gij test
FAIL: verify execution - bytecode->native test
FAIL: verify -O3 execution - source compiled test
FAIL: verify execution - gij test
FAIL: verify -O3 execution - bytecode->native test
Running
/home/packages/gcc/snap/tst/gcc-20050828/libjava/testsuite/libjava.loader/loader.exp
...
FAIL:
/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite/TestEarlyGC.exe
execution -
/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite/TestEarlyGC.exe
FAIL:
/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite/TestLeak.exe
execution -
/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite/TestLeak.exe
FAIL:
/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite/TestMultiple.exe
execution -
/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite/TestMultiple.exe
FAIL:
/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite/TestParent.exe
execution -
/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite/TestParent.exe
Running
/home/packages/gcc/snap/tst/gcc-20050828/libjava/testsuite/libjava.mauve/mauve.exp
...
Running
/home/packages/gcc/snap/tst/gcc-20050828/libjava/testsuite/libjava.special/special.exp
...
FAIL: pr21115 run
Running
/home/packages/gcc/snap/tst/gcc-20050828/libjava/testsuite/libjava.verify/verify.exp
...
=== libjava Summary ===
# of expected passes 1783
# of unexpected failures 1081
# of expected failures 4
# of untested testcases 1089
make[2]: *** [check-DEJAGNU] Error 1
make[2]: Leaving directory
`/home/packages/gcc/snap/tst/build486/i486-linux-gnu/libjava/testsuite'
make[1]: *** [check-am] Error 2
--
Summary: [4.1 regression] 1081 test failures in libjava, when
configured for i486-linux
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: debian-gcc at lists dot debian dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: i486-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23602
next reply other threads:[~2005-08-28 16:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 16:41 debian-gcc at lists dot debian dot org [this message]
2005-08-28 17:20 ` [Bug target/23602] " debian-gcc at lists dot debian dot org
2005-08-28 21:58 ` pinskia at gcc dot gnu dot org
2005-08-29 21:08 ` debian-gcc at lists dot debian dot org
2005-08-30 2:46 ` rth at gcc dot gnu dot org
2005-08-30 6:00 ` rth at gcc dot gnu dot org
2005-08-30 7:33 ` debian-gcc at lists dot debian dot org
2005-08-31 10:17 ` debian-gcc at lists dot debian dot org
2005-08-31 14:12 ` debian-gcc at lists dot debian dot org
2005-09-02 21:39 ` rth at gcc dot gnu dot org
2005-09-02 21:46 ` tromey at gcc dot gnu dot org
2005-09-02 22:09 ` rth at gcc dot gnu dot org
2005-09-02 22:21 ` debian-gcc at lists dot debian dot org
2005-09-05 13:26 ` debian-gcc at lists dot debian dot org
2005-09-26 13:23 ` debian-gcc at lists dot debian dot org
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=20050828164012.23602.debian-gcc@lists.debian.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).