public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57632] Operator new overloads with stdc++11 enabled looses exception specifier (MacOsX)
Date: Fri, 07 Jan 2022 05:49:49 +0000	[thread overview]
Message-ID: <bug-57632-4-u2oVrwy0LG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57632-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So the defect report against C++ was closed as not a defect:

http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_closed.html#967 .
The related one
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_closed.html#1948 dealing with
noexcept was also closed as not a defect.


So GCC is correct, There is no bug here.

  parent reply	other threads:[~2022-01-07  5:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  5:51 [Bug c++/57632] New: " basv@odd-e.com
2013-06-17  9:45 ` [Bug c++/57632] " paolo.carlini at oracle dot com
2022-01-07  5:49 ` pinskia at gcc dot gnu.org [this message]
2022-01-07 12:47 ` redi at gcc dot gnu.org
2022-01-07 23:47 ` pinskia at gcc dot gnu.org
2022-01-08  3:38 ` [Bug c++/57632] diagonistic for different exception specifier/noexcept if decl is declared twice should be improved pinskia 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-57632-4-u2oVrwy0LG@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).