public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103758] bogus warning: misspelled term 'decl' in format; use 'declaration' instead [-Wformat-diag] Date: Mon, 03 Jan 2022 21:27:47 +0000 [thread overview] Message-ID: <bug-103758-4-m6BtYgYDdP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103758-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103758 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:bb936163e28fdbe1a751c55d5e5975e036322a3d commit r12-6195-gbb936163e28fdbe1a751c55d5e5975e036322a3d Author: Marek Polacek <polacek@redhat.com> Date: Fri Dec 17 14:34:12 2021 -0500 c-family: Have -Wformat-diag accept "decl-specifier" [PR103758] I'm tired of seeing cp/parser.c:15923:55: warning: misspelled term 'decl' in format; use 'declaration' instead [-Wformat-diag] cp/parser.c:15925:57: warning: misspelled term 'decl' in format; use 'declaration' instead [-Wformat-diag] every time I compile cp/parser.c, which happens...a lot. I'd like my compilation to be free of warnings, otherwise I'm going to miss some important ones. "decl-specifiers" is a C++ grammar term; it is not actual code, so should not be wrapped with %< %>. I hope we can accept it as an exception in check_tokens. It was surrounded by %< %> in cp_parser_decl_specifier_seq, so fix that. In passing, fix a misspelling in missspellings. PR c++/103758 gcc/c-family/ChangeLog: * c-format.c (check_tokens): Accept "decl-specifier*". gcc/cp/ChangeLog: * parser.c (cp_parser_decl_specifier_seq): Replace %<decl-specifier%> with %qD. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/constexpr-condition.C: Adjust dg-error.
next prev parent reply other threads:[~2022-01-03 21:27 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-17 17:30 [Bug c++/103758] New: " mpolacek at gcc dot gnu.org 2021-12-17 17:31 ` [Bug c++/103758] " jason at gcc dot gnu.org 2021-12-17 17:31 ` mpolacek at gcc dot gnu.org 2021-12-17 19:27 ` mpolacek at gcc dot gnu.org 2022-01-03 21:27 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-03 21:28 ` mpolacek at gcc dot gnu.org 2022-01-05 8:48 ` marxin at gcc dot gnu.org 2022-01-05 15:14 ` mpolacek at gcc dot gnu.org 2022-01-05 15:32 ` jakub at gcc dot gnu.org 2022-01-05 15:33 ` jakub at gcc dot gnu.org 2022-01-05 15:38 ` mpolacek at gcc dot gnu.org 2022-01-05 15:49 ` msebor at gcc dot gnu.org 2022-01-06 0:43 ` cvs-commit at gcc dot gnu.org 2022-01-17 18:33 ` cvs-commit at gcc dot gnu.org 2022-01-17 18:33 ` mpolacek at gcc dot gnu.org 2022-01-17 18:39 ` mpolacek at gcc dot gnu.org 2022-01-17 18:45 ` jakub at gcc dot gnu.org 2022-01-17 18:47 ` mpolacek at gcc dot gnu.org 2022-01-17 21:27 ` cvs-commit 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-103758-4-m6BtYgYDdP@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).