public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Andrew Klein" <klein@newmonics.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3380: [LinuxPPC] bootstrap comparison failed on java/parse.o
Date: Wed, 27 Nov 2002 06:21:00 -0000 [thread overview]
Message-ID: <20021119213605.31994.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/3380; it has been noted by GNATS.
From: "Andrew Klein" <klein@newmonics.com>
To: <bangerth@dealii.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
<klein@newmonics.com>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: bootstrap/3380: [LinuxPPC] bootstrap comparison failed on java/parse.o
Date: Tue, 19 Nov 2002 14:35:16 -0700
This turned out to be a hardware problem, sorry.
----- Original Message -----
From: <bangerth@dealii.org>
To: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <klein@newmonics.com>;
<nobody@gcc.gnu.org>
Sent: Tuesday, November 19, 2002 1:20 PM
Subject: Re: bootstrap/3380: [LinuxPPC] bootstrap comparison failed on
java/parse.o
> Old Synopsis: bootstrap comparison failed on java/parse.o
> New Synopsis: [LinuxPPC] bootstrap comparison failed on java/parse.o
>
> State-Changed-From-To: open->feedback
> State-Changed-By: bangerth
> State-Changed-When: Tue Nov 19 12:20:42 2002
> State-Changed-Why:
> This is a rather old bootstrap failure. Can you please
> check whether this still happens with newer versions of gcc
> and report your findings?
>
> Thanks
> Wolfgang
>
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
r=3380
next reply other threads:[~2002-11-19 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 6:21 Andrew Klein [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 7:25 bangerth
2002-11-26 14:56 bangerth
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=20021119213605.31994.qmail@sources.redhat.com \
--to=klein@newmonics.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).