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++/98249] [9/10/11/12 Regression] Improper ADL on the `arg` in `new (arg) T`
Date: Mon, 11 Apr 2022 21:31:27 +0000	[thread overview]
Message-ID: <bug-98249-4-mZq6ITcwcb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98249-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:d087b59527a658a4de13febbb593edbf03339e93

commit r12-8093-gd087b59527a658a4de13febbb593edbf03339e93
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Apr 11 13:06:05 2022 -0400

    c++: operator new lookup [PR98249]

    The standard says, as we quote in the comment just above, that if we don't
    find operator new in the allocated type, it should be looked up in the
    global scope.  This is specifically ::, not just any namespace, and we
    already give an error for an operator new declared in any other namespace.

            PR c++/98249

    gcc/cp/ChangeLog:

            * call.cc (build_operator_new_call): Just look in ::.

    gcc/testsuite/ChangeLog:

            * g++.dg/lookup/new3.C: New test.

  parent reply	other threads:[~2022-04-11 21:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 21:56 [Bug c++/98249] New: " arthur.j.odwyer at gmail dot com
2021-09-19  6:15 ` [Bug c++/98249] " pinskia at gcc dot gnu.org
2021-09-19  6:21 ` [Bug c++/98249] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-04-11 17:06 ` jason at gcc dot gnu.org
2022-04-11 21:31 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-12 20:14 ` [Bug c++/98249] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-05-12 21:14 ` [Bug c++/98249] [9/10 " cvs-commit at gcc dot gnu.org
2022-05-13 17:41 ` [Bug c++/98249] [9 " cvs-commit at gcc dot gnu.org
2022-05-13 17:50 ` 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-98249-4-mZq6ITcwcb@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).