public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/9946: [3.2 regression] destructor is not called for temporary object
@ 2003-04-25 19:50 jbuck
  0 siblings, 0 replies; 2+ messages in thread
From: jbuck @ 2003-04-25 19:50 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, kuznets, nobody, vakatov, vasilche

Synopsis: [3.2 regression] destructor is not called for temporary object

State-Changed-From-To: analyzed->closed
State-Changed-By: jbuck
State-Changed-When: Fri Apr 25 19:50:13 2003
State-Changed-Why:
    Fixed for the next release (3.3).

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


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

* Re: c++/9946: [3.2 regression] destructor is not called for temporary object
@ 2003-03-04 22:41 bangerth
  0 siblings, 0 replies; 2+ messages in thread
From: bangerth @ 2003-03-04 22:41 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, kuznets, nobody, vakatov, vasilche

Old Synopsis: destructor is not called for temporary object
New Synopsis: [3.2 regression] destructor is not called for temporary object

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Mar  4 22:41:50 2003
State-Changed-Why:
    Confirmed, a regression in 3.2 w.r.t 3.0. It is fixed in
    3.3 and mainline, though.
    
    W.

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


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

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

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-25 19:50 c++/9946: [3.2 regression] destructor is not called for temporary object jbuck
  -- strict thread matches above, loose matches on Subject: below --
2003-03-04 22:41 bangerth

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