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 tree-optimization/104012] [12 regression] -Wformat-truncation warnings not taking previous length check into account Date: Fri, 14 Jan 2022 17:29:54 +0000 [thread overview] Message-ID: <bug-104012-4-QCSHjoT1B0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104012-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104012 --- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> --- To expand a bit on the fuzziness at level 1. The logic is documented under the -Wformat-overflow warning like so: Numeric arguments that are known to be bounded to a subrange of their type, or string arguments whose output is bounded either by their directive’s precision or by a finite set of string literals, are assumed to take on the value within the range that results in the most bytes on output.
prev parent reply other threads:[~2022-01-14 17:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-13 16:01 [Bug c++/104012] New: " eike@sf-mail.de 2022-01-13 16:04 ` [Bug tree-optimization/104012] [12 regression] " pinskia at gcc dot gnu.org 2022-01-13 19:58 ` eike@sf-mail.de 2022-01-13 21:49 ` msebor at gcc dot gnu.org 2022-01-14 14:14 ` eike@sf-mail.de 2022-01-14 16:20 ` msebor at gcc dot gnu.org 2022-01-14 17:29 ` msebor at gcc dot gnu.org [this message]
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-104012-4-QCSHjoT1B0@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).