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: msp430: fix -Wunused-variable warnings Date: Tue, 19 Dec 2023 10:53:42 +0000 (GMT) [thread overview] Message-ID: <20231219105342.5C65C3861816@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=eade7580251b53909ad8adcf3b89e4a8c608fd79 commit eade7580251b53909ad8adcf3b89e4a8c608fd79 Author: Mike Frysinger <vapier@gentoo.org> Date: Fri Dec 15 22:22:35 2023 -0500 sim: msp430: fix -Wunused-variable warnings Diff: --- 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 b34d23e8e84..ee5a6544f2f 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;
reply other threads:[~2023-12-19 10:53 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=20231219105342.5C65C3861816@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: 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).