public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/20040] A new expression must check the access level of delete operator
Date: Fri, 21 Jan 2022 20:18:23 +0000	[thread overview]
Message-ID: <bug-20040-4-2RHabOFlmf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-20040-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:847a8301add0a316767878342c1367948835c181

commit r12-6808-g847a8301add0a316767878342c1367948835c181
Author: Jason Merrill <jason@redhat.com>
Date:   Fri Jan 21 12:49:03 2022 -0500

    c++: class array new checking [PR104084]

    My patch for PR20040 made us stop exiting early from build_new_1 in
    cases of trivial initialization if there's a class operator delete; as a
    result, code later in the function needs to handle this case properly.

            PR c++/104084
            PR c++/20040

    gcc/cp/ChangeLog:

            * init.cc (build_new_1): Only pull out TARGET_EXPR_INITIAL if
            alloc_expr is a TARGET_EXPR.

    gcc/testsuite/ChangeLog:

            * g++.dg/init/new50.C: New test.

  parent reply	other threads:[~2022-01-21 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20040-4@http.gcc.gnu.org/bugzilla/>
2022-01-06 21:19 ` jason at gcc dot gnu.org
2022-01-07 22:12 ` cvs-commit at gcc dot gnu.org
2022-01-21 20:18 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-28  4:40 ` jason at gcc dot gnu.org
     [not found] <bug-20040-10087@http.gcc.gnu.org/bugzilla/>
2006-09-08 20:30 ` amylaar at gcc dot gnu dot org
2005-02-18  4:11 [Bug c++/20040] New: " msadoghi at ca dot ibm dot com
2005-02-18  4:12 ` [Bug c++/20040] " pinskia at gcc dot gnu dot 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-20040-4-2RHabOFlmf@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).