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 bootstrap/100431] Fixes to enable compiling with -Werror=format-security Date: Tue, 11 May 2021 13:57:57 +0000 [thread overview] Message-ID: <bug-100431-4-0K4HMHwXds@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100431-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100431 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- %< and %> are GCC diagnostics format specifiers, not printf. They are more similar to e.g. GNU printf %m , something that doesn't take any va_arg, but is interpreted. Try printf ("%m\n"); vs. printf ("%s", "%m\n"); to see the difference. Anyway, for this case either using the conditional directly in the cpp_warning_with_line argument instead of in initializer of a temporary, or two cpp_warning_with_line calls each with a separate string would do. Anyway, I strongly doubt your patch covers everything, I can see e.g. gcc/c/c-convert.c:81:31: warning: format not a string literal and no format arguments [-Wformat-security] gcc/c/c-typeck.c:3681:28: warning: format not a string literal and no format arguments [-Wformat-security] gcc/c/c-typeck.c:4433:42: warning: format not a string literal and no format arguments [-Wformat-security] gcc/c/c-typeck.c:6587:43: warning: format not a string literal and no format arguments [-Wformat-security] gcc/c/c-typeck.c:11679:42: warning: format not a string literal and no format arguments [-Wformat-security] gcc/c-family/c-common.c:6358:30: warning: format not a string literal and no format arguments [-Wformat-security] gcc/c-family/c-common.c:6362:33: warning: format not a string literal and no format arguments [-Wformat-security] gcc/fold-const.c:303:42: warning: format not a string literal and no format arguments [-Wformat-security] gcc/ipa-devirt.c:951:47: warning: format not a string literal and no format arguments [-Wformat-security] gcc/analyzer/program-state.cc:1153:20: warning: format not a string literal and no format arguments [-Wformat-security] gcc/diagnostic.c:1887:52: warning: format not a string literal and no format arguments [-Wformat-security] gcc/cp/cvt.c:725:26: warning: format not a string literal and no format arguments [-Wformat-security] gcc/cp/error.c:799:20: warning: spurious leading punctuation sequence ‘<’ in format [-Wformat-diag] gcc/cp/error.c:799:20: warning: spurious trailing punctuation sequence ‘>’ in format [-Wformat-diag] gcc/cp/error.c:799:20: warning: spurious leading punctuation sequence ‘<’ in format [-Wformat-diag] gcc/cp/error.c:799:20: warning: spurious trailing punctuation sequence ‘>’ in format [-Wformat-diag] gcc/cp/decl.c:3485:22: warning: format not a string literal and no format arguments [-Wformat-security] gcc/cp/typeck.c:4721:24: warning: format not a string literal and no format arguments [-Wformat-security] gcc/cp/typeck.c:6630:24: warning: format not a string literal and no format arguments [-Wformat-security] gcc/cp/pt.c:19640:20: warning: format not a string literal and no format arguments [-Wformat-security] gcc/collect2.c:2422:37: warning: format not a string literal and no format arguments [-Wformat-security] gcc/collect-utils.c:200:37: warning: format not a string literal and no format arguments [-Wformat-security] gcc/lto-wrapper.c:1606:31: warning: format not a string literal and no format arguments [-Wformat-security] and you've only touched the gcc/diagnostic.c case from that.
next prev parent reply other threads:[~2021-05-11 13:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-05 11:24 [Bug bootstrap/100431] New: " joey.dumont at gmail dot com 2021-05-05 11:25 ` [Bug bootstrap/100431] " joey.dumont at gmail dot com 2021-05-05 11:47 ` jakub at gcc dot gnu.org 2021-05-11 13:45 ` joey.dumont at gmail dot com 2021-05-11 13:57 ` jakub at gcc dot gnu.org [this message] 2021-06-20 2:33 ` joey.dumont 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-100431-4-0K4HMHwXds@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).