From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH/committed 18/21] sim: msp430: fix -Wunused-variable warnings
Date: Tue, 19 Dec 2023 05:51:52 -0500 [thread overview]
Message-ID: <20231219105155.10433-18-vapier@gentoo.org> (raw)
In-Reply-To: <20231219105155.10433-1-vapier@gentoo.org>
---
sim/msp430/msp430-sim.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/sim/msp430/msp430-sim.c b/sim/msp430/msp430-sim.c
index b34d23e8e84d..ee5a6544f2f4 100644
--- a/sim/msp430/msp430-sim.c
+++ b/sim/msp430/msp430-sim.c
@@ -796,13 +796,12 @@ msp430_cio (SIM_DESC sd)
perform. */
sim_cpu *cpu = STATE_CPU (sd, 0);
struct msp430_cpu_state *msp430_cpu = MSP430_SIM_CPU (cpu);
- unsigned char raw_parms[13];
unsigned char parms[8];
long length;
int command;
unsigned char buffer[512];
long ret_buflen = 0;
- long fd, addr, len, rv;
+ long fd, len, rv;
sim_core_read_buffer (sd, cpu, 0, parms, msp430_cpu->cio_buffer, 5);
length = CIO_I (0);
@@ -1045,7 +1044,6 @@ msp430_step_once (SIM_DESC sd)
sim_cpu *cpu = STATE_CPU (sd, 0);
struct msp430_cpu_state *msp430_cpu = MSP430_SIM_CPU (cpu);
Get_Byte_Local_Data ld;
- unsigned char buf[100];
int i;
int opsize;
unsigned int opcode_pc;
@@ -1053,8 +1051,7 @@ msp430_step_once (SIM_DESC sd)
MSP430_Opcode_Decoded *opcode = &opcode_buf;
int s1, s2, result;
int u1 = 0, u2, uresult;
- int c = 0, reg;
- int sp;
+ int c = 0;
int carry_to_use;
int n_repeats;
int rept;
--
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 ` Mike Frysinger [this message]
2023-12-19 10:51 ` [PATCH/committed 19/21] sim: moxie: " Mike Frysinger
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-18-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).