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++/50871] [C++0x] G++ fails to reject explicitly-defaulted function definition with different exception spec in system headers Date: Wed, 26 Oct 2011 13:47:00 -0000 [thread overview] Message-ID: <bug-50871-4-TFjXioGQcc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50871-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50871 --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-10-26 13:46:45 UTC --- Yes they are. Not doing that would be a good idea
next prev parent reply other threads:[~2011-10-26 13:47 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-25 22:29 [Bug c++/50871] New: [C++0x] G++ fails to reject explicitly-defaulted function definition with different exception spec redi at gcc dot gnu.org 2011-10-26 10:15 ` [Bug c++/50871] [C++0x] G++ fails to reject explicitly-defaulted function definition with different exception spec in system headers paolo.carlini at oracle dot com 2011-10-26 10:41 ` redi at gcc dot gnu.org 2011-10-26 11:31 ` paolo.carlini at oracle dot com 2011-10-26 13:38 ` jason at gcc dot gnu.org 2011-10-26 13:47 ` redi at gcc dot gnu.org [this message] 2011-10-27 13:17 ` paolo.carlini at oracle dot com 2011-10-27 13:31 ` redi at gcc dot gnu.org 2011-10-27 13:35 ` paolo.carlini at oracle dot com 2011-11-10 22:50 ` [Bug libstdc++/50871] " jason at gcc dot gnu.org 2011-12-03 15:35 ` redi at gcc dot gnu.org 2014-04-04 17:06 ` redi at gcc dot gnu.org 2014-06-24 15:00 ` redi at gcc dot gnu.org 2024-09-26 19:40 ` [Bug libstdc++/50871] libstdc++ should be built with -Wpedantic and/or -Wsystem-headers sjames 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-50871-4-TFjXioGQcc@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: linkBe 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).