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/104119] [12 Regression] unexpected -Wformat-overflow after strlen in ILP32 since Ranger integration Date: Thu, 03 Feb 2022 20:37:11 +0000 [thread overview] Message-ID: <bug-104119-4-qZp8im72cw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104119-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104119 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> --- The warning has been avoided in this case by using the size of the source array as the upper bound. The heuristic the warning uses is still in place so when the size of the source array isn't known (e.g., when it's a flexible array member) it will still trigger.
prev parent reply other threads:[~2022-02-03 20:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-19 14:54 [Bug tree-optimization/104119] New: Wrong -Werror=format-overflow= since r12-5014-g6b8b959675a3e14c marxin at gcc dot gnu.org 2022-01-19 14:55 ` [Bug tree-optimization/104119] " marxin at gcc dot gnu.org 2022-01-19 17:44 ` [Bug tree-optimization/104119] unexpected -Wformat-overflow after strlen in ILP32 since Ranger integration msebor at gcc dot gnu.org 2022-01-19 17:59 ` pinskia at gcc dot gnu.org 2022-01-19 18:07 ` [Bug tree-optimization/104119] [12 Regression] " msebor at gcc dot gnu.org 2022-01-20 1:21 ` msebor at gcc dot gnu.org 2022-01-20 7:43 ` rguenth at gcc dot gnu.org 2022-02-03 20:31 ` cvs-commit at gcc dot gnu.org 2022-02-03 20:37 ` 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-104119-4-qZp8im72cw@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).