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++/104148] [11/12 Regression] -Wformat warning no longer warns about () wrapped args since r11-2457 Date: Thu, 20 Jan 2022 19:11:21 +0000 [thread overview] Message-ID: <bug-104148-4-h4BCHh3l7N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104148-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104148 --- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> --- I suspect the unwanted suppression is because check_function_argument_recurse() calls warning_suppressed_p (param) instead of warning_suppressed_p (param, <option>) (for each of the warnings it checks). So any other warning suppressed for a call (or its arguments) like -Wparentheses will also suppress -Wformat and friends. Or it could also be because of one the outstanding suppress_warning() calls with no warning option id: grep suppress_warning gcc/cp/*.cc | grep -v OPT) gcc/cp/call.cc: suppress_warning (c /* Suppress all warnings. */); gcc/cp/call.cc: suppress_warning (decl); gcc/cp/constraint.cc: suppress_warning (t); gcc/cp/coroutines.cc: suppress_warning (r); /* We don't want a warning about this. */ gcc/cp/coroutines.cc: suppress_warning (r); /* We don't want a warning about this. */ gcc/cp/coroutines.cc: suppress_warning (rethrow); gcc/cp/coroutines.cc: suppress_warning (rethrow); gcc/cp/cp-gimplify.cc: suppress_warning (*stmt_p); gcc/cp/cp-gimplify.cc: suppress_warning (TREE_OPERAND (*stmt_p, 1)); gcc/cp/except.cc: suppress_warning (rethrow); gcc/cp/init.cc: suppress_warning (cleanup); gcc/cp/init.cc: suppress_warning (init_expr); gcc/cp/init.cc: suppress_warning (stmt_expr /* What warning? */); gcc/cp/pt.cc: suppress_warning (tldcl); gcc/cp/semantics.cc: suppress_warning (DECL_EXPR_DECL (data.stmts[0]) /* What warning? */); gcc/cp/semantics.cc: suppress_warning (DECL_EXPR_DECL (data.stmts[0]) /* Wat warning? */); gcc/cp/typeck.cc: suppress_warning (arg /* What warning? */); gcc/cp/typeck.cc: suppress_warning (rval /* What warning? */);
next prev parent reply other threads:[~2022-01-20 19:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 18:14 [Bug c++/104148] New: " jakub at gcc dot gnu.org 2022-01-20 18:15 ` [Bug c++/104148] " jakub at gcc dot gnu.org 2022-01-20 18:18 ` jakub at gcc dot gnu.org 2022-01-20 18:50 ` jakub at gcc dot gnu.org 2022-01-20 19:01 ` jakub at gcc dot gnu.org 2022-01-20 19:11 ` msebor at gcc dot gnu.org [this message] 2022-01-20 19:49 ` jakub at gcc dot gnu.org 2022-01-21 21:45 ` cvs-commit at gcc dot gnu.org 2022-01-21 21:47 ` [Bug c++/104148] [11 " jakub 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-104148-4-h4BCHh3l7N@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).