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 middle-end/104077] bogus/missing -Wdangling-pointer Date: Thu, 03 Mar 2022 21:02:42 +0000 [thread overview] Message-ID: <bug-104077-4-IxjZSlVf9s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104077-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104077 Bug 104077 depends on bug 104761, which changed state. Bug 104761 Summary: [12 Regression] bogus -Wdangling-pointer with cleanup and infinite loop https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104761 What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED
next prev parent reply other threads:[~2022-03-03 21:02 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 22:12 [Bug middle-end/104077] New: " msebor at gcc dot gnu.org 2022-01-17 22:12 ` [Bug middle-end/104077] " msebor at gcc dot gnu.org 2022-01-18 16:49 ` msebor at gcc dot gnu.org 2022-02-04 7:17 ` rguenth at gcc dot gnu.org 2022-02-08 23:01 ` msebor at gcc dot gnu.org 2022-03-03 21:02 ` msebor at gcc dot gnu.org [this message] 2022-03-15 0:27 ` msebor at gcc dot gnu.org 2022-04-25 7:57 ` rguenth at gcc dot gnu.org 2022-04-27 10:03 ` [Bug middle-end/104077] [meta-bug] " rguenth at gcc dot gnu.org 2022-12-11 1:55 ` pinskia at gcc dot gnu.org 2022-12-12 11:20 ` rguenth at gcc dot gnu.org 2023-02-15 17:39 ` mpolacek at gcc dot gnu.org 2023-06-23 10:30 ` 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-104077-4-IxjZSlVf9s@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).