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/104215] bogus -Wuse-after-free=3 due to forwprop moving a pointer test after realloc Date: Wed, 26 Jan 2022 16:39:01 +0000 [thread overview] Message-ID: <bug-104215-4-OnYVeoHMJD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104215-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104215 --- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> --- The kernel false positive is discussed in bug 104069 comment 13. I don't think it's related to this issue but you're of course right that this warning isn't immune to false positives. That's true for all warnings in GCC but especially so for the flow-dependent ones that depend on optimizers. They're inherent in their design. The best we can do is try to minimize them but we'll never be able to avoid them all. But I'm tired of having this argument each time a false positive pops up that can't be easily avoided so I won't be working on any more warnings in the future.
next prev parent reply other threads:[~2022-01-26 16:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 21:49 [Bug tree-optimization/104215] New: " msebor at gcc dot gnu.org 2022-01-25 8:07 ` [Bug tree-optimization/104215] " rguenth at gcc dot gnu.org 2022-01-25 18:17 ` msebor at gcc dot gnu.org 2022-01-25 18:20 ` msebor at gcc dot gnu.org 2022-01-25 18:34 ` rguenther at suse dot de 2022-01-25 23:04 ` msebor at gcc dot gnu.org 2022-01-26 7:23 ` rguenther at suse dot de 2022-01-26 16:39 ` msebor at gcc dot gnu.org [this message] 2022-01-29 22:28 ` pinskia 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-104215-4-OnYVeoHMJD@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).