public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christian Joensson <christian@j-son.org>
To: Joe Buck <Joe.Buck@synopsys.COM>
Cc: Mark Mitchell <mark@codesourcery.com>,
	Michael Chastain <mec.gnu@mindspring.com>,
	gcc@gcc.gnu.org
Subject: Re: GCC 3.4.2 Release Candidate Available
Date: Wed, 01 Sep 2004 05:21:00 -0000	[thread overview]
Message-ID: <20040901071715.A9135@fw.j-son.org> (raw)
In-Reply-To: <20040831165229.A1723@synopsys.com>; from Joe.Buck@synopsys.COM on Tue, Aug 31, 2004 at 04:52:29PM -0700

On Tue, Aug 31, 2004 at 04:52:29PM -0700, Joe Buck wrote:
> On Tue, Aug 31, 2004 at 08:55:06AM -0700, Joe Buck wrote:
> > I successfully built RC1 and ran tests on a funny old HPUX 11.0 machine.
> > ...
> > I also have a sparc-sun-solaris2.8 build that has completed but has not
> > yet finished running tests.  The results will show up soon on
> > gcc-testresults.
> 
> Results now available:
> http://gcc.gnu.org/ml/gcc-testresults/2004-08/msg01228.html
> 
> There are large numbers of g77 failures.

The same holds for sparc-linux, see, e.g., 
http://gcc.gnu.org/ml/gcc-testresults/2004-08/msg01194.html

Due to bus error.. maybe glibc related?

Cheers,

/ChJ

  parent reply	other threads:[~2004-09-01  5:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  4:28 Michael Chastain
2004-08-31  4:51 ` Mark Mitchell
2004-08-31  4:59   ` Michael Chastain
2004-08-31 16:56   ` Joe Buck
     [not found]     ` <20040831165229.A1723@synopsys.com>
2004-09-01  5:21       ` Christian Joensson [this message]
2004-09-01  5:24         ` Andrew Pinski
  -- strict thread matches above, loose matches on Subject: below --
2004-08-31 18:43 Harald Dunkel
2004-08-31 18:53 ` Daniel Jacobowitz
2004-08-31 22:01   ` Harald Dunkel
2004-08-29 23:17 Mark Mitchell
2004-08-31 17:57 ` Janis Johnson

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=20040901071715.A9135@fw.j-son.org \
    --to=christian@j-son.org \
    --cc=Joe.Buck@synopsys.COM \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=mec.gnu@mindspring.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).