public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: lerdsuwa@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4447: c++ ICE (segfault in mangle.c). Regression from 2.95.x!
Date: Fri, 09 Nov 2001 13:16:00 -0000 [thread overview]
Message-ID: <20011118065601.13432.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c++/4447; it has been noted by GNATS.
From: lerdsuwa@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
jbuck@synopsys.COM, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/4447: c++ ICE (segfault in mangle.c). Regression from 2.95.x!
Date: 18 Nov 2001 06:54:12 -0000
Synopsis: c++ ICE (segfault in mangle.c). Regression from 2.95.x!
State-Changed-From-To: analyzed->closed
State-Changed-By: lerdsuwa
State-Changed-When: Sat Nov 17 22:54:12 2001
State-Changed-Why:
Fixed in the main trunk.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4447&database=gcc
next reply other threads:[~2001-11-18 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-09 13:16 lerdsuwa [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-09 12:56 lerdsuwa
2001-10-07 4:19 lerdsuwa
2001-10-02 16:16 jbuck
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=20011118065601.13432.qmail@sourceware.cygnus.com \
--to=lerdsuwa@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).