public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107256] Contradictory circular noexcept-specifier is accepted
Date: Fri, 14 Oct 2022 09:06:53 +0000 [thread overview]
Message-ID: <bug-107256-4-acFdq5pno0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107256-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107256
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=107186
CC| |mpolacek at gcc dot gnu.org
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Started to be accepted with commit g:78f7607db4c53f8cfe4653a6c91c0328bc2854c3
Author: Marek Polacek
Date: Sat Jun 22 16:14:30 2019
PR c++/86476 - noexcept-specifier is a complete-class context.
next prev parent reply other threads:[~2022-10-14 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 2:06 [Bug c++/107256] New: " de34 at live dot cn
2022-10-14 9:06 ` redi at gcc dot gnu.org [this message]
2022-10-18 19:33 ` [Bug c++/107256] " mpolacek 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-107256-4-acFdq5pno0@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).