From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][pushed] Remove dead code.
Date: Wed, 4 May 2022 14:49:24 +0200 [thread overview]
Message-ID: <53a19169-b79a-742e-6646-18aff8ce65d5@suse.cz> (raw)
gcc/ChangeLog:
* gengtype-state.cc (read_a_state_token): Remove dead code.
* ipa-profile.cc (ipa_profile_read_summary_section): Likewise.
---
gcc/gengtype-state.cc | 22 +++++++++++-----------
gcc/ipa-profile.cc | 1 -
2 files changed, 11 insertions(+), 12 deletions(-)
diff --git a/gcc/gengtype-state.cc b/gcc/gengtype-state.cc
index ea566af3249..dfd9ea52785 100644
--- a/gcc/gengtype-state.cc
+++ b/gcc/gengtype-state.cc
@@ -473,43 +473,43 @@ read_a_state_token (void)
{
case 'a':
obstack_1grow (&bstring_obstack, '\a');
- c = getc (state_file);
+ getc (state_file);
break;
case 'b':
obstack_1grow (&bstring_obstack, '\b');
- c = getc (state_file);
+ getc (state_file);
break;
case 't':
obstack_1grow (&bstring_obstack, '\t');
- c = getc (state_file);
+ getc (state_file);
break;
case 'n':
obstack_1grow (&bstring_obstack, '\n');
- c = getc (state_file);
+ getc (state_file);
break;
case 'v':
obstack_1grow (&bstring_obstack, '\v');
- c = getc (state_file);
+ getc (state_file);
break;
case 'f':
obstack_1grow (&bstring_obstack, '\f');
- c = getc (state_file);
+ getc (state_file);
break;
case 'r':
obstack_1grow (&bstring_obstack, '\r');
- c = getc (state_file);
+ getc (state_file);
break;
case '"':
obstack_1grow (&bstring_obstack, '\"');
- c = getc (state_file);
+ getc (state_file);
break;
case '\\':
obstack_1grow (&bstring_obstack, '\\');
- c = getc (state_file);
+ getc (state_file);
break;
case ' ':
obstack_1grow (&bstring_obstack, ' ');
- c = getc (state_file);
+ getc (state_file);
break;
case 'x':
{
@@ -520,7 +520,7 @@ read_a_state_token (void)
fatal_reading_state
(NULL_STATE_TOKEN,
"Lexical error in string hex escape");
- c = getc (state_file);
+ getc (state_file);
break;
}
default:
diff --git a/gcc/ipa-profile.cc b/gcc/ipa-profile.cc
index ffdcb4476e8..b74d77f2c95 100644
--- a/gcc/ipa-profile.cc
+++ b/gcc/ipa-profile.cc
@@ -481,7 +481,6 @@ ipa_profile_read_summary_section (struct lto_file_decl_data *file_data,
for (i = 0; i < count; i++)
{
index = streamer_read_uhwi (ib);
- encoder = file_data->symtab_node_encoder;
node
= dyn_cast<cgraph_node *> (lto_symtab_encoder_deref (encoder, index));
--
2.36.0
next reply other threads:[~2022-05-04 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 12:49 Martin Liška [this message]
2022-05-04 13:20 ` Andreas Schwab
2022-05-04 14:20 ` Martin Liška
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=53a19169-b79a-742e-6646-18aff8ce65d5@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).