public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-3083] analyzer: remove unused variables Date: Wed, 5 Oct 2022 11:35:38 +0000 (GMT) [thread overview] Message-ID: <20221005113538.80C6B3858017@sourceware.org> (raw) https://gcc.gnu.org/g:bcc27369910b818047bca466fbcef6a3034dfc7f commit r13-3083-gbcc27369910b818047bca466fbcef6a3034dfc7f Author: Martin Liska <mliska@suse.cz> Date: Wed Oct 5 13:33:24 2022 +0200 analyzer: remove unused variables Fixes: gcc/analyzer/call-summary.h:103:13: warning: private field 'm_called_fn' is not used [-Wunused-private-field] gcc/analyzer/engine.cc:1631:24: warning: unused parameter 'uncertainty' [-Wunused-parameter] gcc/analyzer/ChangeLog: * call-summary.cc (call_summary_replay::call_summary_replay): Remove unused variable and arguments. * call-summary.h: Likewise. * engine.cc (exploded_node::on_stmt): Likewise. (exploded_node::replay_call_summaries): Likewise. (exploded_node::replay_call_summary): Likewise. * exploded-graph.h (class exploded_node): Likewise. Diff: --- gcc/analyzer/call-summary.cc | 1 - gcc/analyzer/call-summary.h | 1 - gcc/analyzer/engine.cc | 5 +---- gcc/analyzer/exploded-graph.h | 2 -- 4 files changed, 1 insertion(+), 8 deletions(-) diff --git a/gcc/analyzer/call-summary.cc b/gcc/analyzer/call-summary.cc index 9d8716da96e..a8e881472ea 100644 --- a/gcc/analyzer/call-summary.cc +++ b/gcc/analyzer/call-summary.cc @@ -171,7 +171,6 @@ call_summary_replay::call_summary_replay (const call_details &cd, call_summary *summary, const extrinsic_state &ext_state) : m_cd (cd), - m_called_fn (called_fn), m_summary (summary), m_ext_state (ext_state) { diff --git a/gcc/analyzer/call-summary.h b/gcc/analyzer/call-summary.h index f4c5ff0b3aa..07cd3f53ce6 100644 --- a/gcc/analyzer/call-summary.h +++ b/gcc/analyzer/call-summary.h @@ -100,7 +100,6 @@ private: const region *convert_region_from_summary_1 (const region *); const call_details &m_cd; - function *m_called_fn; call_summary *m_summary; const extrinsic_state &m_ext_state; diff --git a/gcc/analyzer/engine.cc b/gcc/analyzer/engine.cc index b4deee50f1f..735b5a3c061 100644 --- a/gcc/analyzer/engine.cc +++ b/gcc/analyzer/engine.cc @@ -1439,7 +1439,6 @@ exploded_node::on_stmt (exploded_graph &eg, snode, as_a <const gcall *> (stmt), state, - uncertainty, path_ctxt, called_fn, called_fn_data, @@ -1598,7 +1597,6 @@ exploded_node::replay_call_summaries (exploded_graph &eg, const supernode *snode, const gcall *call_stmt, program_state *state, - uncertainty_t *uncertainty, path_context *path_ctxt, function *called_fn, per_function_data *called_fn_data, @@ -1612,7 +1610,7 @@ exploded_node::replay_call_summaries (exploded_graph &eg, /* Each summary will call bifurcate on the PATH_CTXT. */ for (auto summary : called_fn_data->m_summaries) - replay_call_summary (eg, snode, call_stmt, state, uncertainty, + replay_call_summary (eg, snode, call_stmt, state, path_ctxt, called_fn, summary, ctxt); path_ctxt->terminate_path (); @@ -1628,7 +1626,6 @@ exploded_node::replay_call_summary (exploded_graph &eg, const supernode *snode, const gcall *call_stmt, program_state *old_state, - uncertainty_t *uncertainty, path_context *path_ctxt, function *called_fn, call_summary *summary, diff --git a/gcc/analyzer/exploded-graph.h b/gcc/analyzer/exploded-graph.h index ea4a890b9ce..11e46cab160 100644 --- a/gcc/analyzer/exploded-graph.h +++ b/gcc/analyzer/exploded-graph.h @@ -271,7 +271,6 @@ class exploded_node : public dnode<eg_traits> const supernode *snode, const gcall *call_stmt, program_state *state, - uncertainty_t *uncertainty, path_context *path_ctxt, function *called_fn, per_function_data *called_fn_data, @@ -280,7 +279,6 @@ class exploded_node : public dnode<eg_traits> const supernode *snode, const gcall *call_stmt, program_state *state, - uncertainty_t *uncertainty, path_context *path_ctxt, function *called_fn, call_summary *summary,
reply other threads:[~2022-10-05 11:35 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221005113538.80C6B3858017@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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).