public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/35035] [4.3 Regression] Has any one managed to run the libjava test suite on powerpc-apple-darwin9?
Date: Thu, 31 Jan 2008 12:28:00 -0000 [thread overview]
Message-ID: <20080131122855.8722.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35035-12313@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from dominiq at lps dot ens dot fr 2008-01-31 12:28 -------
> bootstrap started on ppc-darwin.
After having applied the patch in the right directory and an incremental make
on Darwin9, I still ahve the same failures:
FAIL: PR9577 run
FAIL: longfield run
FAIL: shortfield run
Running /opt/gcc/gcc-4.3-work/libjava/testsuite/libjava.jar/jar.exp ...
FAIL: TestClosureGC run
FAIL: /opt/gcc/gcc-4.3-work/libjava/testsuite/libjava.jar/TestClosureGC.jar
execution - gij test
FAIL: simple run
FAIL: /opt/gcc/gcc-4.3-work/libjava/testsuite/libjava.jar/simple.jar execution
- gij test
Running /opt/gcc/gcc-4.3-work/libjava/testsuite/libjava.jni/jni.exp ...
FAIL: PR15133 run
FAIL: PR18116 run
FAIL: PR28178 run
FAIL: bytebuffer run
FAIL: calls run
FAIL: cxxtest run
FAIL: directbuffer run
FAIL: field run
FAIL: final_method run
FAIL: findclass run
FAIL: findclass2 run
FAIL: iface run
FAIL: init run
I am now starting a fresh build (~12 hours).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35035
next prev parent reply other threads:[~2008-01-31 12:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 22:10 [Bug java/35035] New: " dominiq at lps dot ens dot fr
2008-01-30 22:13 ` [Bug java/35035] " dominiq at lps dot ens dot fr
2008-01-30 22:18 ` andreast at gcc dot gnu dot org
2008-01-31 9:49 ` [Bug java/35035] [4.3 Regression] " rguenth at gcc dot gnu dot org
2008-01-31 10:01 ` dominiq at lps dot ens dot fr
2008-01-31 10:11 ` rguenth at gcc dot gnu dot org
2008-01-31 10:12 ` rguenth at gcc dot gnu dot org
2008-01-31 10:35 ` dominiq at lps dot ens dot fr
2008-01-31 11:12 ` andreast at gcc dot gnu dot org
2008-01-31 12:28 ` dominiq at lps dot ens dot fr [this message]
2008-01-31 12:51 ` andreast at gcc dot gnu dot org
2008-01-31 13:30 ` andreast at gcc dot gnu dot org
2008-01-31 14:14 ` rguenth at gcc dot gnu dot org
2008-01-31 14:19 ` rguenth at gcc dot gnu dot org
2008-01-31 18:39 ` andreast at gcc dot gnu dot org
2008-01-31 23:10 ` dominiq at lps dot ens dot fr
2008-02-03 12:46 ` rguenth at gcc dot gnu dot org
2008-02-03 20:47 ` dominiq at lps dot ens dot fr
2008-02-03 20:56 ` dominiq at lps dot ens dot fr
2008-02-03 21:22 ` andreast at gcc dot gnu dot org
2008-02-03 21:40 ` rguenth at gcc dot gnu dot org
2008-02-03 21:40 ` rguenth at gcc dot gnu dot org
2008-02-03 21:42 ` howarth at nitro dot med dot uc dot edu
2008-02-03 21:57 ` dominiq at lps dot ens dot fr
2008-02-03 22:08 ` andreast at gcc dot gnu dot org
2008-02-03 22:15 ` dominiq at lps dot ens dot fr
2008-02-03 22:19 ` howarth at nitro dot med dot uc dot edu
2008-02-04 13:32 ` dominiq at lps dot ens dot fr
2008-02-04 13:48 ` andreast at gcc dot gnu dot org
2008-02-04 14:01 ` dominiq at lps dot ens dot fr
2008-02-04 14:54 ` howarth at nitro dot med dot uc dot edu
2008-02-04 18:36 ` howarth at nitro dot med dot uc dot edu
2008-02-04 20:39 ` rguenther at suse dot de
2008-02-04 21:13 ` rguenth at gcc dot gnu dot org
2008-02-04 21:13 ` rguenth at gcc dot gnu dot org
2008-02-05 19:27 ` dominiq at lps dot ens dot fr
2008-02-05 19:58 ` howarth at nitro dot med dot uc dot edu
2008-02-05 20:01 ` pinskia at gmail dot com
2008-02-05 20:10 ` rguenther at suse dot de
2008-02-05 20:13 ` howarth at nitro dot med dot uc dot edu
2008-02-05 20:26 ` dominiq at lps dot ens dot fr
2008-02-05 20:30 ` rguenther at suse dot de
2008-03-12 14:26 ` rguenth at gcc dot gnu dot org
2008-03-12 14:30 ` rguenth at gcc dot gnu 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=20080131122855.8722.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).