public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8499: [3.3 regression] [x86-64] Tree checking failure on after error reported
Date: Thu, 13 Mar 2003 01:16:00 -0000	[thread overview]
Message-ID: <20030313011600.25848.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/8499; it has been noted by GNATS.

From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: gcc-gnats@gcc.gnu.org, jh@suse.cz, gcc-bugs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: c/8499: [3.3 regression] [x86-64] Tree checking failure on after
 error reported
Date: Thu, 13 Mar 2003 02:11:16 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8499
 
 Since hardly anyone has access to this hardware, and the audit trail for 
 this PR is empty, this is unlikely to be fixed for 3.3.  Maybe you or 
 somebody else at SuSE can have a look at it?  It's just a tree checking 
 failure, and it hasn't been confirmed since its arrival date (4 months 
 ago...).
 
 Greetz
 Steven
 
 


             reply	other threads:[~2003-03-13  1:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13  1:16 Steven Bosscher [this message]
2003-03-14 13:39 zlomek

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=20030313011600.25848.qmail@sources.redhat.com \
    --to=s.bosscher@student.tudelft.nl \
    --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).