public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sakovacs@freemail.hu Subject: Re: c++/9872: [3.2 regression] wrong code with eliding constructors Date: Mon, 03 Mar 2003 15:38:00 -0000 [thread overview] Message-ID: <20030303153859.19689.qmail@sources.redhat.com> (raw) Old Synopsis: temporary destructor not called? New Synopsis: [3.2 regression] wrong code with eliding constructors State-Changed-From-To: feedback->analyzed State-Changed-By: bangerth State-Changed-When: Mon Mar 3 15:38:59 2003 State-Changed-Why: Confirmed. This is a regression in 3.2 with respect to 2.95. It is fixed in 3.3 and mainline, though. I keep it open, though, since a) a regression, and b) maybe someone from the Linux vendor side wants to fix it if they are going to stay with 3.2.x for some more time. Sandor's reduced testcase is attached as attachment 3. Thanks, Sandor, for the detective work! W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9872
next reply other threads:[~2003-03-03 15:38 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-03 15:38 bangerth [this message] 2003-04-28 11:49 ehrhardt
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=20030303153859.19689.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=sakovacs@freemail.hu \ /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: linkBe 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).