public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/61818] unused code fails to be removed after dom1, thread updated Date: Sun, 26 Dec 2021 21:28:16 +0000 [thread overview] Message-ID: <bug-61818-4-sp2a6F2ozC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61818-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61818 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Known to work| |7.1.0 Resolution|--- |FIXED Known to fail| |5.1.0, 6.1.0 Target Milestone|--- |7.0 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Fixed in GCC 7. What was missing was not optimizing: ppnode.1_5 = &_15->m_next; if (&n == ppnode.1_5) Even though n never escaped.
next prev parent reply other threads:[~2021-12-26 21:28 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-16 9:55 [Bug tree-optimization/61818] New: " manjian2006 at gmail dot com 2014-07-16 11:22 ` [Bug tree-optimization/61818] " rguenth at gcc dot gnu.org 2021-12-26 21:28 ` pinskia at gcc dot gnu.org [this message] 2024-05-16 12:47 ` 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-61818-4-sp2a6F2ozC@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).