public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52202] New: [C++11][DR 1376] Should not extend lifetime of temporary wrapped in static_cast to reference type Date: Fri, 10 Feb 2012 21:29:00 -0000 [thread overview] Message-ID: <bug-52202-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52202 Bug #: 52202 Summary: [C++11][DR 1376] Should not extend lifetime of temporary wrapped in static_cast to reference type Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: jason@gcc.gnu.org // Core 1376 // { dg-options -std=c++0x } extern "C" void abort(); bool x; struct T { ~T() { if (x) abort (); } }; int main() { T&& r = static_cast<T&&>(T()); x = true; }
next reply other threads:[~2012-02-10 21:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-10 21:29 jason at gcc dot gnu.org [this message] 2021-04-06 7:07 ` [Bug c++/52202] " jens.maurer at gmx dot net 2021-04-07 2:12 ` mpolacek at gcc dot gnu.org 2021-04-07 2:19 ` cvs-commit at gcc dot gnu.org 2021-04-07 2:20 ` mpolacek at gcc dot gnu.org
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=bug-52202-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: 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).