public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: mmitchel@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8724: [3.2 regression] explicit destructor call for incomplete class allowed
Date: Mon, 10 Mar 2003 12:06:00 -0000 [thread overview]
Message-ID: <20030310120600.9119.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/8724; it has been noted by GNATS.
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, eker@csl.sri.com, gcc-bugs@gcc.gnu.org,
mmitchel@gcc.gnu.org
Cc:
Subject: Re: c++/8724: [3.2 regression] explicit destructor call for incomplete
class allowed
Date: Mon, 10 Mar 2003 13:01:06 +0100 (CET)
Just for the record:
The problem seems to be fixed on the 3.3 branch (as well as on
mainline). It just remains open on the 3.2 branch.
Regards,
Volker
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8724
next reply other threads:[~2003-03-10 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 12:06 Volker Reichelt [this message]
2003-04-25 21:06 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=20030310120600.9119.qmail@sources.redhat.com \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=mmitchel@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).