public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] sim: cr16: fix -Wunused-variable warnings
Date: Tue, 19 Dec 2023 10:52:36 +0000 (GMT)	[thread overview]
Message-ID: <20231219105236.5DDB43864856@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=303dc26d24b0c9e61d3193678b12336e68dbf3eb

commit 303dc26d24b0c9e61d3193678b12336e68dbf3eb
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Fri Dec 15 21:47:20 2023 -0500

    sim: cr16: fix -Wunused-variable warnings

Diff:
---
 sim/cr16/interp.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/sim/cr16/interp.c b/sim/cr16/interp.c
index d45fa6349d3..9a2363a6d52 100644
--- a/sim/cr16/interp.c
+++ b/sim/cr16/interp.c
@@ -67,7 +67,7 @@ struct hash_entry hash_table[MAX_HASH+1];
 INLINE static long
 hash(unsigned long long insn, int format)
 { 
-  unsigned int i = 4, tmp;
+  unsigned int i = 4;
   if (format)
     {
       while ((insn >> i) != 0) i +=4;
@@ -113,7 +113,7 @@ INLINE static void
 get_operands (operand_desc *s, uint64_t ins, int isize, int nops)
 {
   uint32_t i, opn = 0, start_bit = 0, op_type = 0; 
-  int32_t op_size = 0, mask = 0;
+  int32_t op_size = 0;
 
   if (isize == 1) /* Trunkcate the extra 16 bits of INS.  */
     ins = ins >> 16;
@@ -397,7 +397,6 @@ sim_open (SIM_OPEN_KIND kind, struct host_callback_struct *cb,
   struct simops *s;
   struct hash_entry *h;
   static int init_p = 0;
-  char **p;
   int i;
   SIM_DESC sd = sim_state_alloc (kind, cb);
   SIM_ASSERT (STATE_MAGIC (sd) == SIM_MAGIC_NUMBER);

                 reply	other threads:[~2023-12-19 10:52 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=20231219105236.5DDB43864856@sourceware.org \
    --to=vapier@sourceware.org \
    --cc=gdb-cvs@sourceware.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).