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++/48370] G++ fails to extend reference temporary lifetime in some situations Date: Sat, 05 Nov 2011 03:28:00 -0000 [thread overview] Message-ID: <bug-48370-4-GEotJPakH9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48370-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48370 --- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> 2011-11-05 03:28:09 UTC --- Author: jason Date: Sat Nov 5 03:28:05 2011 New Revision: 181001 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=181001 Log: PR c++/48370 * decl.c (cp_finish_decl): Run cleanups in the right order. Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/decl.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/g++.dg/init/lifetime1.C
prev parent reply other threads:[~2011-11-05 3:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-30 17:35 [Bug c++/48370] New: " jason at gcc dot gnu.org 2011-08-08 13:56 ` [Bug c++/48370] " jason at gcc dot gnu.org 2011-11-04 12:54 ` jason at gcc dot gnu.org 2011-11-04 14:46 ` jason at gcc dot gnu.org 2011-11-05 3:28 ` jason at gcc dot gnu.org [this message]
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-48370-4-GEotJPakH9@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).