public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: libjava testresults (Was: basic-improvements call for testers)
Date: Mon, 16 Dec 2002 08:36:00 -0000	[thread overview]
Message-ID: <1040055972.16026.560.camel@elsschot> (raw)
In-Reply-To: <20021216121524.GA8359@elsschot>

On Mon, 2002-12-16 at 13:15, Mark Wielaard wrote:
> Hi (java@gcc.gnu.org added to the CC),
> [...]
> Also my tests on powerpc on the mainline don't look that bad.

But please note the posting from Jerry Quinn "3.4 bib failed to
bootstrap java on ppc" on the main gcc mailinglist:

        I just tried to build 3.4 bib last night on
        powerpc-unknown-gnu-linux
        and had the java bootstrap fail.
        
        stage1/xgcc -Bstage1/ -B/usr/local/powerpc-unknown-linux-gnu/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes  -fno-common  -DHAVE_CONFIG_H    -I. -Ijava -I../../gcc/gcc -I../../gcc/gcc/java -I../../gcc/gcc/config -I../../gcc/gcc/../include ../../gcc/gcc/java/jcf-write.c -o java/jcf-write.o
        ../../gcc/gcc/java/jcf-write.c: In function `init_jcf_state':
        ../../gcc/gcc/java/jcf-write.c:2853: internal compiler error: Segmentation fault

That probably means that my autobuilder on ppc which tests libgcj
against the Mauve testsuite will probably die as soon as the bib branch
is merged into mainline :(

If it helps I can setup that machine to run the 3.4-bi branch tonight.
But that might take a while (more then 10 hours) since it is a slow
machine and I will have to clear up some disk space for a new CVS tree.

Cheers,

Mark

  reply	other threads:[~2002-12-16 16:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14 11:22 basic-improvements call for testers Zack Weinberg
2002-12-14 11:30 ` Jan Hubicka
2002-12-14 14:26 ` Andreas Tobler
2002-12-15 15:09   ` Geoff Keating
2002-12-15 15:28     ` Zack Weinberg
2002-12-16 11:45       ` Andreas Tobler
2002-12-16 11:49       ` Geoff Keating
2002-12-16 12:03         ` Daniel Jacobowitz
2002-12-16 12:53           ` Geoff Keating
2002-12-14 16:16 ` Andrew Pinski
2002-12-15 11:01 ` Mark Mitchell
2002-12-16  4:51 ` libjava testresults (Was: basic-improvements call for testers) Mark Wielaard
2002-12-16  8:36   ` Mark Wielaard [this message]
2002-12-17  5:23     ` Mark Wielaard
2002-12-18  2:25       ` Mark Wielaard
2002-12-18  5:18   ` libjava testresults Zack Weinberg
2002-12-18 10:23     ` 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=1040055972.16026.560.camel@elsschot \
    --to=mark@klomp.org \
    --cc=gcc@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --cc=zack@codesourcery.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).