public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97237] [10/11 Regression] static_assert does not accept fpermissive code Date: Tue, 29 Sep 2020 10:21:14 +0000 [thread overview] Message-ID: <bug-97237-4-jChS1yaIsA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97237-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97237 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- It surprises me -fpermissive ever accepted such bogosities. Also using -fpermissive with C++11 and later code is very weird, -fpermissive is about letting some very old unmaintained code compile, but using that together with C++11 features doesn't make sense.
next prev parent reply other threads:[~2020-09-29 10:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-29 8:26 [Bug c++/97237] New: " lutztonineubert at gmail dot com 2020-09-29 10:11 ` [Bug c++/97237] " redi at gcc dot gnu.org 2020-09-29 10:21 ` jakub at gcc dot gnu.org [this message] 2020-09-29 10:43 ` redi at gcc dot gnu.org 2020-10-16 12:19 ` rguenth at gcc dot gnu.org 2020-10-24 20:09 ` lutztonineubert at gmail dot com 2020-11-05 7:01 ` lutztonineubert at gmail dot com
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-97237-4-jChS1yaIsA@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).