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/104746] False positive for -Wformat-overflow=2 since r12-7033-g3c9f762ad02f398c Date: Mon, 07 Mar 2022 23:34:32 +0000 [thread overview] Message-ID: <bug-104746-4-KNhAUdNDpo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104746-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104746 --- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> --- Martin, since the warning is working correctly (even if it's arguably not as clear as it could be), I'd like us to close this. If you agree, can you please go ahead and mark this as resolved (either invalid or wontfix)?
next prev parent reply other threads:[~2022-03-07 23:34 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-01 13:55 [Bug tree-optimization/104746] New: [12 Regression] " marxin at gcc dot gnu.org 2022-03-01 13:55 ` [Bug tree-optimization/104746] " marxin at gcc dot gnu.org 2022-03-01 18:36 ` msebor at gcc dot gnu.org 2022-03-03 9:04 ` marxin at gcc dot gnu.org 2022-03-03 10:00 ` marxin at gcc dot gnu.org 2022-03-03 10:10 ` marxin at gcc dot gnu.org 2022-03-03 18:21 ` msebor at gcc dot gnu.org 2022-03-03 18:25 ` [Bug tree-optimization/104746] " msebor at gcc dot gnu.org 2022-03-03 21:20 ` amacleod at redhat dot com 2022-03-04 0:24 ` msebor at gcc dot gnu.org 2022-03-07 23:34 ` msebor at gcc dot gnu.org [this message] 2022-03-08 12:33 ` marxin at gcc dot gnu.org 2022-03-08 15:53 ` marxin at gcc dot gnu.org 2022-03-14 16:49 ` msebor at gcc dot gnu.org 2022-03-14 19:04 ` amacleod at redhat dot com 2022-03-14 20:32 ` msebor 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-104746-4-KNhAUdNDpo@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).