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/105499] inconsistency between -Werror=c++-compat and g++ in __extension__ block Date: Mon, 31 Oct 2022 14:57:38 +0000 [thread overview] Message-ID: <bug-105499-4-9g3WBg5mwh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105499-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105499 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- __extension__ is supposed to disable compatibility warnings since they are written in GNU C. Just happens that you enabled compatibility warnings to C++ which are also disabled. This is the misunderstanding of what the warning and what __extension__ does.
next prev parent reply other threads:[~2022-10-31 14:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-06 0:12 [Bug c++/105499] New: " vincent-gcc at vinc17 dot net 2022-05-06 4:09 ` [Bug c++/105499] " egallager at gcc dot gnu.org 2022-05-06 9:17 ` vincent-gcc at vinc17 dot net 2022-10-31 7:45 ` [Bug c/105499] " pinskia at gcc dot gnu.org 2022-10-31 7:53 ` pinskia at gcc dot gnu.org 2022-10-31 12:34 ` vincent-gcc at vinc17 dot net 2022-10-31 14:17 ` vincent-gcc at vinc17 dot net 2022-10-31 14:57 ` pinskia at gcc dot gnu.org [this message] 2022-11-01 3:21 ` vincent-gcc at vinc17 dot net
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-105499-4-9g3WBg5mwh@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).