From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][pushed] remove dead member variable in dom_jt_state
Date: Thu, 30 Jun 2022 10:29:06 +0200 [thread overview]
Message-ID: <c1f1167e-157a-0f6e-34bb-2b35bc30ac1e@suse.cz> (raw)
Hi.
I'm going to push the following clean-up.
Martin
gcc/ChangeLog:
* tree-ssa-dom.cc (pass_dominator::execute): Remove m_ranger as
it is unused.
---
gcc/tree-ssa-dom.cc | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/gcc/tree-ssa-dom.cc b/gcc/tree-ssa-dom.cc
index dcaf4672b66..9b6520fd2dd 100644
--- a/gcc/tree-ssa-dom.cc
+++ b/gcc/tree-ssa-dom.cc
@@ -588,9 +588,8 @@ record_edge_info (basic_block bb)
class dom_jt_state : public jt_state
{
public:
- dom_jt_state (const_and_copies *copies, avail_exprs_stack *avails,
- gimple_ranger *ranger)
- : m_copies (copies), m_avails (avails), m_ranger (ranger)
+ dom_jt_state (const_and_copies *copies, avail_exprs_stack *avails)
+ : m_copies (copies), m_avails (avails)
{
}
void push (edge e) override
@@ -613,7 +612,6 @@ public:
private:
const_and_copies *m_copies;
avail_exprs_stack *m_avails;
- gimple_ranger *m_ranger;
};
void
@@ -794,7 +792,7 @@ pass_dominator::execute (function *fun)
gimple_ranger *ranger = enable_ranger (fun);
path_range_query path_query (/*resolve=*/true, ranger);
dom_jt_simplifier simplifier (avail_exprs_stack, ranger, &path_query);
- dom_jt_state state (const_and_copies, avail_exprs_stack, ranger);
+ dom_jt_state state (const_and_copies, avail_exprs_stack);
jump_threader threader (&simplifier, &state);
dom_opt_dom_walker walker (CDI_DOMINATORS,
&threader,
--
2.36.1
next reply other threads:[~2022-06-30 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 8:29 Martin Liška [this message]
2022-06-30 8:42 ` 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=c1f1167e-157a-0f6e-34bb-2b35bc30ac1e@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@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: 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).