public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schaub.johannes at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48562] New: Prematurely destroys initializer_list array when using new-expression
Date: Mon, 11 Apr 2011 21:45:00 -0000	[thread overview]
Message-ID: <bug-48562-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: Prematurely destroys initializer_list array when using
                    new-expression
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: schaub.johannes@googlemail.com


The C++0x spec requires that GCC destroys the backing-up array at "delete p",
but GCC appears to destroy it immediately after the first declaration (as
checked by using a class type that has a side-effecting destructor). 

    auto *p= new initializer_list<int>{1, 2, 3}; 
    { auto q(*p); }
    delete p;


             reply	other threads:[~2011-04-11 21:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 21:45 schaub.johannes at googlemail dot com [this message]
2011-04-19  9:20 ` [Bug c++/48562] " amonakov at gcc dot gnu.org
2011-09-23 22:09 ` [Bug c++/48562] [C++0x] " paolo.carlini at oracle dot com
2011-09-23 22:25 ` [Bug c++/48562] [C++0x] warn about uses of initializer_list that will lead to dangling pointers jason at gcc dot gnu.org
2011-09-23 22:26 ` paolo.carlini at oracle dot com
2011-09-23 22:35 ` paolo.carlini at oracle dot com
2011-09-25 11:08 ` paolo.carlini at oracle dot com
2011-09-25 14:53 ` schaub.johannes at googlemail dot com
2011-09-25 14:58 ` paolo.carlini at oracle dot com

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-48562-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: 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).