public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "David Abrahams" <david.abrahams@rcn.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5068: ice in g++
Date: Sun, 27 Jan 2002 17:36:00 -0000 [thread overview]
Message-ID: <20020128013600.30756.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5068; it has been noted by GNATS.
From: "David Abrahams" <david.abrahams@rcn.com>
To: <rodrigc@gcc.gnu.org>
Cc:
Subject: Re: c++/5068: ice in g++
Date: Tue, 11 Dec 2001 06:58:37 -0500
I forgot the password used to stick followups in the gnats DB :(
The bug certainly looks the same, but to confirm it I have to update my CVS,
and there's quite a load on your CVS server right now. I'll let you know.
-Dave
----- Original Message -----
From: <rodrigc@gcc.gnu.org>
To: <david.abrahams@rcn.com>; <gcc-bugs@gcc.gnu.org>;
<gcc-gnats@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <jason@tishler.net>;
<nobody@gcc.gnu.org>
Sent: Tuesday, December 11, 2001 12:44 AM
Subject: Re: c++/5068: ice in g++
> Synopsis: ice in g++
>
> State-Changed-From-To: open->feedback
> State-Changed-By: rodrigc
> State-Changed-When: Mon Dec 10 21:43:47 2001
> State-Changed-Why:
> I believe that this bug is a duplicate of PR 3394, which
> has been fixed:
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3394&database=gcc
>
> Can you confirm this?
>
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5068&databa
se=gcc
>
next reply other threads:[~2002-01-28 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 17:36 David Abrahams [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-27 17:33 rodrigc
2001-12-10 21:46 rodrigc
2001-12-10 21:44 rodrigc
2001-12-10 20:06 david.abrahams
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=20020128013600.30756.qmail@sources.redhat.com \
--to=david.abrahams@rcn.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).