public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104761] [12 Regression] False positive -Wdangling-pointer warning on NetworkManager since r12-6606 Date: Wed, 02 Mar 2022 15:51:29 +0000 [thread overview] Message-ID: <bug-104761-4-oVF74dpPfL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104761-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104761 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I think the problem is in: if (!bitmap_set_bit (visited, bb->index)) /* Avoid cycles. */ return true; pass_waccess::use_after_inval_p When walking the bbs from use_bb: <bb 6> : error.0_3 = error; // <--- use_stmt _4 = error.0_3->t; _5 = addrbin.s; _6 = qux (_5); corge (_6, _4); <bb 7> : goto <bb 7>; [INV] The 7->7 edge is just EDGE_FALLTHRU and we visit bb 7 and then return true even when there was an endless loop which means it can't reach inval_stmt.
next prev parent reply other threads:[~2022-03-02 15:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-02 15:19 [Bug middle-end/104761] New: " jakub at gcc dot gnu.org 2022-03-02 15:19 ` [Bug middle-end/104761] " jakub at gcc dot gnu.org 2022-03-02 15:51 ` jakub at gcc dot gnu.org [this message] 2022-03-02 16:07 ` jakub at gcc dot gnu.org 2022-03-02 20:35 ` msebor at gcc dot gnu.org 2022-03-02 23:16 ` [Bug middle-end/104761] [12 Regression] bogus -Wdangling-pointer with cleanup and infinite loop msebor at gcc dot gnu.org 2022-03-03 21:02 ` cvs-commit at gcc dot gnu.org 2022-03-03 21:02 ` 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-104761-4-oVF74dpPfL@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).