public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104761] [12 Regression] bogus -Wdangling-pointer with cleanup and infinite loop Date: Thu, 03 Mar 2022 21:02:11 +0000 [thread overview] Message-ID: <bug-104761-4-HAdvaSMpO5@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 #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>: https://gcc.gnu.org/g:51149a05b8cc8e4fc5a77a65857894daa371de89 commit r12-7467-g51149a05b8cc8e4fc5a77a65857894daa371de89 Author: Martin Sebor <msebor@redhat.com> Date: Thu Mar 3 13:58:00 2022 -0700 Call mark_dfs_back_edges before testing EDGE_DFS_BACK [PR104761]. Resolves: PR middle-end/104761 - bogus -Wdangling-pointer with cleanup and infinite loop gcc/ChangeLog: PR middle-end/104761 * gimple-ssa-warn-access.cc (pass_waccess::execute): Call mark_dfs_back_edges. gcc/testsuite/ChangeLog: PR middle-end/104761 * g++.dg/warn/Wdangling-pointer-4.C: New test. * gcc.dg/Wdangling-pointer-4.c: New test.
next prev parent reply other threads:[~2022-03-03 21:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-02 15:19 [Bug middle-end/104761] New: [12 Regression] False positive -Wdangling-pointer warning on NetworkManager since r12-6606 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 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 [this message] 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-HAdvaSMpO5@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).