From: Jeff Law <jeffreyalaw@gmail.com>
To: "Martin Liška" <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Remove unused variable.
Date: Thu, 13 May 2021 07:43:37 -0600 [thread overview]
Message-ID: <6fb5767b-de55-5de6-fc41-8b09da04078a@gmail.com> (raw)
In-Reply-To: <81be254c-5f4a-1bb5-3ec3-fdbc539590e9@suse.cz>
On 5/13/2021 3:06 AM, Martin Liška wrote:
> Addresses the following clang warning:
> gcc/tree-ssa-dom.c:652:33: warning: private field 'm_simplifier' is
> not used [-Wunused-private-field]
>
> Ready for master?
> Thanks
>
> gcc/ChangeLog:
>
> * tree-ssa-dom.c: Remove m_simplifier.
I wonder if Aldy's refactor accidentally dropped the ephemeral
simplifications based on the threading path equivalences which is what I
think this is supposed to be supporting. Given that the refactor didn't
cause any regressions, if that capability did get dropped, it couldn't
be too important anymore.
OK for the trunk,
Jeff
next prev parent reply other threads:[~2021-05-13 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 9:06 Martin Liška
2021-05-13 13:43 ` Jeff Law [this message]
2021-05-13 19:48 ` Aldy Hernandez
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=6fb5767b-de55-5de6-fc41-8b09da04078a@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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: link
Be 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).