public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/8724: [3.2 regression] explicit destructor call for incomplete class allowed
@ 2003-04-25 21:06 jbuck
  0 siblings, 0 replies; 2+ messages in thread
From: jbuck @ 2003-04-25 21:06 UTC (permalink / raw)
  To: eker, gcc-bugs, gcc-prs, mmitchel

Synopsis: [3.2 regression] explicit destructor call for incomplete class allowed

State-Changed-From-To: analyzed->closed
State-Changed-By: jbuck
State-Changed-When: Fri Apr 25 21:06:35 2003
State-Changed-Why:
    Fixed for 3.3.

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: c++/8724: [3.2 regression] explicit destructor call for incomplete class allowed
@ 2003-03-10 12:06 Volker Reichelt
  0 siblings, 0 replies; 2+ messages in thread
From: Volker Reichelt @ 2003-03-10 12:06 UTC (permalink / raw)
  To: mmitchel; +Cc: gcc-prs

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
 
 


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-04-25 21:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-25 21:06 c++/8724: [3.2 regression] explicit destructor call for incomplete class allowed jbuck
  -- strict thread matches above, loose matches on Subject: below --
2003-03-10 12:06 Volker Reichelt

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).