public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101940] Implement -fignored-attributes Date: Tue, 17 Aug 2021 15:31:15 +0000 [thread overview] Message-ID: <bug-101940-4-4hOvza2jmZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101940-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101940 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gcc dot gnu.org Last reconfirmed| |2021-08-17 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> --- If the only thing the new option is meant to control is -Wattributes warnings I tend to agree that adding an optional argument to -Wattributes= would be a natural enhancement. (Similar to -Wnormalized= or -Wsuggest-attribute= except with a free-form string as an argument). I would expect the existing diagnostic pragmas to work with it too: #pragma GCC ignored "-Wattributes=vendor::attr1"
next prev parent reply other threads:[~2021-08-17 15:31 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-16 21:05 [Bug c++/101940] New: " mpolacek at gcc dot gnu.org 2021-08-17 7:48 ` [Bug c++/101940] " rguenth at gcc dot gnu.org 2021-08-17 14:19 ` mpolacek at gcc dot gnu.org 2021-08-17 15:31 ` msebor at gcc dot gnu.org [this message] 2021-08-17 15:49 ` mpolacek at gcc dot gnu.org 2021-09-20 17:07 ` [Bug c++/101940] Implement -Wno-attributes=vendor::attr mpolacek at gcc dot gnu.org 2021-11-10 14:26 ` cvs-commit at gcc dot gnu.org 2021-11-10 14:31 ` 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-101940-4-4hOvza2jmZ@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).