public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: davem@gcc.gnu.org
To: christian@j-son.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: bootstrap/7802: stage2 bootstrap of gcc-3-3 (20020901) failure on sparc32-linux
Date: Thu, 10 Oct 2002 11:29:00 -0000	[thread overview]
Message-ID: <20021010182927.28816.qmail@sources.redhat.com> (raw)

Synopsis: stage2 bootstrap of gcc-3-3 (20020901) failure on sparc32-linux

State-Changed-From-To: open->closed
State-Changed-By: davem
State-Changed-When: Thu Oct 10 11:29:27 2002
State-Changed-Why:
    Verified to not occur anymore with current mainline.
    
    Please, in the future, attach huge *.i preprocessed files
    using the "Add a file attachment:" dialog on the gnats
    bug entry page, don't just cat it into the Description
    field.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7802


             reply	other threads:[~2002-10-10 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 11:29 davem [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-01 12:56 christian

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=20021010182927.28816.qmail@sources.redhat.com \
    --to=davem@gcc.gnu.org \
    --cc=christian@j-son.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).