public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105867] [12/13 Regression] incorrect dangling-pointer warning Date: Mon, 25 Jul 2022 16:10:07 +0000 [thread overview] Message-ID: <bug-105867-4-2b9Rco9LEZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105867-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105867 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gcc dot gnu.org Priority|P3 |P2 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. I don't know how the dataflow of the diagnostic is implemented but to fix this it would need to go backwards from function exits and maintain a set of "killed" locations it would not diagnose in earlier code. Of course it's difficult in general considering global = &local; tem = global; other_global = tem; global = NULL; and here &local escapes to other_global but we'd have to either rely on optimization forwarding &local to tem or we'd have to conservatively assume escaping (what the current code seems to do). The former gets you false negatives while the latter false positives. Note for the testcase the store we diagnose is not dead since it has possible uses via function calls also getting 'this', so optimization is of no help in avoiding the false positive here.
next prev parent reply other threads:[~2022-07-25 16:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-07 0:13 [Bug middle-end/105867] New: " gman at chromium dot org 2022-06-07 6:05 ` [Bug tree-optimization/105867] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-07-25 16:10 ` rguenth at gcc dot gnu.org [this message] 2022-11-13 9:32 ` agriff at tin dot it 2023-03-20 10:48 ` wielkiegie at gmail dot com 2023-05-08 12:24 ` [Bug tree-optimization/105867] [12/13/14 " rguenth 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-105867-4-2b9Rco9LEZ@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).