public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aaw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54197] [4.7/4.8 regression] Lifetime of reference not properly extended
Date: Thu, 16 Aug 2012 18:44:00 -0000	[thread overview]
Message-ID: <bug-54197-4-tzuY59NqZU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54197-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54197

--- Comment #3 from Ollie Wild <aaw at gcc dot gnu.org> 2012-08-16 18:44:01 UTC ---
Author: aaw
Date: Thu Aug 16 18:43:52 2012
New Revision: 190450

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190450
Log:
Fix some cases where lifetimes of temporaries bound to expressions are not
properly extended (Google ref b/6946758).

2012-08-16  Ollie Wild  <aaw@google.com>

    PR c++/54197
    * gcc/cp/call.c (extend_ref_init_temps_1): Handle COMPOUND_EXPR trees.
    * gcc/testsuite/g++.dg/init/lifetime3.C: New test.

Added:
    branches/google/gcc-4_7/gcc/testsuite/g++.dg/init/lifetime3.C
Modified:
    branches/google/gcc-4_7/gcc/cp/ChangeLog.google-4_7
    branches/google/gcc-4_7/gcc/cp/call.c
    branches/google/gcc-4_7/gcc/testsuite/ChangeLog.google-4_7


  parent reply	other threads:[~2012-08-16 18:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 18:54 [Bug c++/54197] New: " ppluzhnikov at google dot com
2012-08-07 19:56 ` [Bug c++/54197] " hjl.tools at gmail dot com
2012-08-08  7:54 ` rguenth at gcc dot gnu.org
2012-08-13 18:04 ` aaw at gcc dot gnu.org
2012-08-13 18:37 ` redi at gcc dot gnu.org
2012-08-16 18:44 ` aaw at gcc dot gnu.org [this message]
2012-08-16 18:47 ` aaw at gcc dot gnu.org
2012-08-31 15:48 ` aaw at gcc dot gnu.org
2012-08-31 17:17 ` aaw at gcc dot gnu.org
2012-08-31 17:24 ` aaw 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-54197-4-tzuY59NqZU@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: link
Be 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).