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/104069] -Werror=use-after-free false positive on elfutils-0.186 Date: Mon, 17 Jan 2022 19:10:31 +0000 [thread overview] Message-ID: <bug-104069-4-38deMcRaIi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104069-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104069 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2022-01-17 Ever confirmed|0 |1 --- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> --- The warning triggers at -O0 and above for an IL that looks like this (at -O1): <bb 6> [local count: 59126544]: # sb_4 = PHI <0B(4), sb_3(5)> b_15 = realloc (sb_4, 1); if (b_15 != 0B) goto <bb 7>; [99.96%] else goto <bb 8>; [0.04%] <bb 7> [local count: 59102893]: <bb 8> [local count: 59126544]: # sb_5 = PHI <sb_4(6), b_15(7)> return sb_5; <<< -Wuse-after-free } All it does is check to see if the use of sb_5 in the return statement is dominated by the realloc call without considering the data flow (i.e., that sb_5 is equal to sb_4 when b_15 is null). The handling of the dominance is too simplistic. Let me look into make it more intelligent.
next prev parent reply other threads:[~2022-01-17 19:10 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 17:18 [Bug c/104069] New: " slyfox at gcc dot gnu.org 2022-01-17 17:27 ` [Bug tree-optimization/104069] " pinskia at gcc dot gnu.org 2022-01-17 17:29 ` slyfox at gcc dot gnu.org 2022-01-17 19:10 ` msebor at gcc dot gnu.org [this message] 2022-01-17 21:52 ` msebor at gcc dot gnu.org 2022-01-18 9:37 ` slyfox at gcc dot gnu.org 2022-01-18 22:03 ` msebor at gcc dot gnu.org 2022-01-18 22:06 ` [Bug middle-end/104069] " msebor at gcc dot gnu.org 2022-01-18 22:17 ` jakub at gcc dot gnu.org 2022-01-18 22:47 ` msebor at gcc dot gnu.org 2022-01-18 22:56 ` jakub at gcc dot gnu.org 2022-01-19 0:51 ` amacleod at redhat dot com 2022-01-19 1:04 ` cvs-commit at gcc dot gnu.org 2022-01-19 20:22 ` msebor at gcc dot gnu.org 2022-01-19 20:24 ` msebor at gcc dot gnu.org 2022-01-19 20:30 ` pinskia at gcc dot gnu.org 2022-01-19 20:31 ` pinskia at gcc dot gnu.org 2022-01-19 20:32 ` msebor at gcc dot gnu.org 2022-01-19 20:34 ` jakub at gcc dot gnu.org 2022-01-19 20:42 ` jakub at gcc dot gnu.org 2022-01-19 20:54 ` msebor at gcc dot gnu.org 2022-01-31 11:18 ` jakub at gcc dot gnu.org 2022-03-17 19:32 ` msebor at gcc dot gnu.org 2022-05-16 14:14 ` eike@sf-mail.de 2022-08-24 8:51 ` vincent at systemli dot org 2022-10-27 16:57 ` mark at gcc dot gnu.org 2022-10-28 7:36 ` slyfox at gcc dot gnu.org 2023-05-10 3:35 ` [Bug middle-end/104069] Wuse-after-free=2 -O0 false positive "may be used" mkaracsony81 at gmail dot com 2023-05-12 7:00 ` slyfox at gcc dot gnu.org 2023-05-12 8:30 ` mkaracsony81 at gmail dot com 2023-05-12 9:08 ` slyfox at gcc dot gnu.org 2023-05-12 13:20 ` mkaracsony81 at gmail dot com 2023-05-12 20:36 ` slyfox at gcc dot gnu.org 2023-05-13 5:07 ` mkaracsony81 at gmail dot com 2023-05-13 5:07 ` mkaracsony81 at gmail dot com 2023-12-17 4:40 ` lavr at ncbi dot nlm.nih.gov
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-104069-4-38deMcRaIi@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).