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++/57510] initializer_list memory leak
Date: Fri, 23 Jan 2015 16:31:00 -0000	[thread overview]
Message-ID: <bug-57510-4-mH9tURsBEU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57510-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57510

--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Fri Jan 23 16:30:00 2015
New Revision: 220047

URL: https://gcc.gnu.org/viewcvs?rev=220047&root=gcc&view=rev
Log:
    PR c++/64314
    PR c++/57510
    * typeck2.c (split_nonconstant_init_1): Remove a sub-CONSTRUCTOR
    that has been completely split out.

Added:
    trunk/gcc/testsuite/g++.dg/init/array38.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/typeck2.c


  parent reply	other threads:[~2015-01-23 16:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 12:23 [Bug c++/57510] New: " matt at ookypooky dot com
2013-06-03 13:09 ` [Bug c++/57510] " redi at gcc dot gnu.org
2013-06-03 14:28 ` paolo.carlini at oracle dot com
2013-07-22 10:42 ` redi at gcc dot gnu.org
2014-12-08 21:03 ` tavianator at gmail dot com
2014-12-10 22:25 ` jason at gcc dot gnu.org
2014-12-12  3:49 ` jason at gcc dot gnu.org
2014-12-12  3:58 ` jason at gcc dot gnu.org
2015-01-23 16:31 ` jason at gcc dot gnu.org [this message]
2020-03-10 20:10 ` [Bug c++/57510] subobjects not destroyed when exception thrown during list-initialization jason 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-57510-4-mH9tURsBEU@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).