From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH/committed 19/21] sim: moxie: fix -Wunused-variable warnings
Date: Tue, 19 Dec 2023 05:51:53 -0500 [thread overview]
Message-ID: <20231219105155.10433-19-vapier@gentoo.org> (raw)
In-Reply-To: <20231219105155.10433-1-vapier@gentoo.org>
---
sim/moxie/interp.c | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/sim/moxie/interp.c b/sim/moxie/interp.c
index ff41e85a184e..214af57daf93 100644
--- a/sim/moxie/interp.c
+++ b/sim/moxie/interp.c
@@ -91,11 +91,6 @@ moxie_store_unsigned_integer (unsigned char *addr, int len, unsigned long val)
}
}
-/* moxie register names. */
-static const char *reg_names[16] =
- { "$fp", "$sp", "$r0", "$r1", "$r2", "$r3", "$r4", "$r5",
- "$r6", "$r7", "$r8", "$r9", "$r10", "$r11", "$r12", "$r13" };
-
/* The machine state.
This state is maintained in host byte order. The fetch/store
@@ -137,7 +132,6 @@ static void
set_initial_gprs (void)
{
int i;
- long space;
/* Set up machine just out of reset. */
cpu.asregs.regs[PC_REGNO] = 0;
@@ -944,7 +938,6 @@ sim_engine_run (SIM_DESC sd,
{
char fname[1024];
int mode = (int) convert_target_flags ((unsigned) cpu.asregs.regs[3]);
- int perm = (int) cpu.asregs.regs[4];
int fd;
sim_core_read_buffer (sd, scpu, read_map, fname,
cpu.asregs.regs[2], 1024);
@@ -1297,7 +1290,7 @@ sim_create_inferior (SIM_DESC sd, struct bfd *prog_bfd,
char * const *argv, char * const *env)
{
char * const *avp;
- int l, argc, i, tp;
+ int argc, i, tp;
sim_cpu *scpu = STATE_CPU (sd, 0); /* FIXME */
if (prog_bfd != NULL)
--
2.43.0
next prev parent reply other threads:[~2023-12-19 10:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 10:51 [PATCH/committed 01/21] sim: common: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 02/21] sim: aarch64: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 03/21] sim: bfin: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 04/21] sim: bpf: " Mike Frysinger
2024-01-03 9:40 ` Jose E. Marchesi
2023-12-19 10:51 ` [PATCH/committed 05/21] sim: cr16: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 06/21] sim: cris: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 07/21] sim: erc32: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 08/21] sim: frv: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 09/21] sim: ft32: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 10/21] sim: h8300: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 11/21] sim: iq2000: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 12/21] sim: lm32: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 13/21] sim: m32r: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 14/21] sim: mcore: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 15/21] sim: microblaze: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 16/21] sim: mips: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 17/21] sim: mn10300: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 18/21] sim: msp430: " Mike Frysinger
2023-12-19 10:51 ` Mike Frysinger [this message]
2023-12-19 10:51 ` [PATCH/committed 20/21] sim: sh: " Mike Frysinger
2023-12-19 10:51 ` [PATCH/committed 21/21] sim: v850: " Mike Frysinger
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=20231219105155.10433-19-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@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).