From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: tromey@redhat.com
Cc: Anthony Green <green@redhat.com>, Adam Megacz <adam@megacz.com>,
java@gcc.gnu.org
Subject: Re: gnu/gcj/io/shs.cc doesn't compile on Solaris 2.5.1 (bootstrap failure)
Date: Fri, 15 Mar 2002 14:45:00 -0000 [thread overview]
Message-ID: <15506.31114.453333.47693@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87n0x9wkdq.fsf@creche.redhat.com>
Tom Tromey writes:
> Rainer> Taking the whole section from java/lang/mprec.h works on both
> Rainer> sparc-sun-solaris2.5.1 (where the bootstrap completes now;
> Rainer> I'll run the testsuite and post results soon) and
> Rainer> alpha-dec-osf4.0f (where shs.c compiles, but I get the same
> Rainer> ICE compiling java/lang/Character.java, details follow).
>
> Thanks. I'll check this in soon.
fine, thanks. For the reference, here are the testsuite results for
libjava on sparc-sun-solaris2.5.1:
=== libjava tests ===
Running target unix
FAIL: PR5902 compilation from bytecode
FAIL: PR5902 -O compilation from bytecode
FAIL: linking cxxtest
FAIL: Invoke_1 execution from source compiled test
FAIL: Invoke_1 execution from bytecode->native test
FAIL: Invoke_1 -O execution from source compiled test
FAIL: Invoke_1 -O execution from bytecode->native test
FAIL: Primes output from source compiled test
FAIL: Primes output from bytecode->native test
FAIL: Primes -O output from source compiled test
FAIL: Primes -O output from bytecode->native test
FAIL: invokethrow execution from source compiled test
FAIL: invokethrow execution from bytecode->native test
FAIL: invokethrow -O execution from source compiled test
FAIL: invokethrow -O execution from bytecode->native test
FAIL: FileHandleGcTest execution from source compiled test
FAIL: FileHandleGcTest execution from bytecode->native test
FAIL: FileHandleGcTest -O execution from source compiled test
FAIL: FileHandleGcTest -O execution from bytecode->native test
=== libjava Summary ===
# of expected passes 2009
# of unexpected failures 19
# of expected failures 19
# of untested testcases 26
Compared to the previous 3.0.5 results
http://gcc.gnu.org/ml/gcc-testresults/2002-03/msg00293.html
they look excellent. One new failure is the Primes test: there's a gc
message interspersed with the (correct) output:
Needed to allocate blacklisted block at 0x1f9000
Maybe this can be disabled in boehm-gc or ignored somehow: unlike the test
output, it is written to stderr, not stdout.
Rainer
next prev parent reply other threads:[~2002-03-15 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200203132014.VAA27030@tamarinde.TechFak.Uni-Bielefeld.DE>
[not found] ` <86henk3xp5.fsf@megacz.com>
2002-03-13 14:40 ` Rainer Orth
2002-03-13 15:18 ` Adam Megacz
2002-03-13 15:40 ` Anthony Green
2002-03-14 2:56 ` Rainer Orth
2002-03-15 13:07 ` Tom Tromey
2002-03-15 13:33 ` Rainer Orth
2002-03-15 13:41 ` Tom Tromey
2002-03-15 14:45 ` Rainer Orth [this message]
2002-04-02 18:49 ` Tom Tromey
2002-03-15 13:43 ` Tom Tromey
2002-03-15 13:49 ` Rainer Orth
2002-03-15 14:01 ` Tom Tromey
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=15506.31114.453333.47693@xayide.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--cc=adam@megacz.com \
--cc=green@redhat.com \
--cc=java@gcc.gnu.org \
--cc=tromey@redhat.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).