From: Mike Frysinger <vapier@gentoo.org>
To: binutils@sourceware.org
Cc: gdb-patches@sourceware.org, hp@axis.com
Subject: [PATCH] cpu: cris: drop some unused vars
Date: Mon, 18 Dec 2023 21:44:23 -0500 [thread overview]
Message-ID: <20231219024423.25287-1-vapier@gentoo.org> (raw)
These fix unused variable warnings in the generated sim.
---
cpu/cris.cpu | 4 ++--
sim/cris/semcrisv10f-switch.c | 2 --
sim/cris/semcrisv32f-switch.c | 2 --
3 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/cpu/cris.cpu b/cpu/cris.cpu
index 97b44581e78b..2e8cb352b2b9 100644
--- a/cpu/cris.cpu
+++ b/cpu/cris.cpu
@@ -2598,7 +2598,7 @@
"move ${Ps},${Rd-sfield}"
(+ Ps RFIX_MOVE_S_R MODE_REGISTER SIZE_FIXED Rd-sfield)
(sequence
- ((SI grno) (SI prno) (SI newval))
+ ((SI prno) (SI newval))
(set prno (regno Ps))
; CGEN-FIXME: Can't use the following and then "grno" below because
; CGEN will emit a "tmp_grno" *also* in decodev32.c:crisv32f_decode
@@ -3837,7 +3837,7 @@
"$Rs,$Rd"
(+ Rd MODE_REGISTER RFIX_BTST SIZE_FIXED Rs)
(sequence
- ((SI tmpd) (SI cnt))
+ ((SI tmpd))
(set tmpd (sll Rd (sub 31 (and Rs 31))))
(setf-move SI tmpd))
)
diff --git a/sim/cris/semcrisv10f-switch.c b/sim/cris/semcrisv10f-switch.c
index a2bf6f1a6305..711d3c049fd5 100644
--- a/sim/cris/semcrisv10f-switch.c
+++ b/sim/cris/semcrisv10f-switch.c
@@ -3181,7 +3181,6 @@ cgen_rtx_error (current_cpu, "move-r-spr: trying to set a read-only special regi
vpc = SEM_NEXT_VPC (sem_arg, pc, 2);
{
- SI tmp_grno;
SI tmp_prno;
SI tmp_newval;
tmp_prno = FLD (f_operand2);
@@ -11777,7 +11776,6 @@ SET_H_VBIT_MOVE (0);
{
SI tmp_tmpd;
- SI tmp_cnt;
tmp_tmpd = SLLSI (GET_H_GR (FLD (f_operand2)), SUBSI (31, ANDSI (GET_H_GR (FLD (f_operand1)), 31)));
{
{
diff --git a/sim/cris/semcrisv32f-switch.c b/sim/cris/semcrisv32f-switch.c
index 8dd455c94e9a..0ff3df5ac848 100644
--- a/sim/cris/semcrisv32f-switch.c
+++ b/sim/cris/semcrisv32f-switch.c
@@ -3108,7 +3108,6 @@ cgen_rtx_error (current_cpu, "move-r-spr: trying to set a read-only special regi
vpc = SEM_NEXT_VPC (sem_arg, pc, 2);
{
- SI tmp_grno;
SI tmp_prno;
SI tmp_newval;
tmp_prno = FLD (f_operand2);
@@ -12047,7 +12046,6 @@ SET_H_VBIT_MOVE (0);
{
SI tmp_tmpd;
- SI tmp_cnt;
tmp_tmpd = SLLSI (GET_H_GR (FLD (f_operand2)), SUBSI (31, ANDSI (GET_H_GR (FLD (f_operand1)), 31)));
{
{
--
2.43.0
next reply other threads:[~2023-12-19 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 2:44 Mike Frysinger [this message]
2023-12-19 3:09 ` Hans-Peter Nilsson
2023-12-19 10:45 ` 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=20231219024423.25287-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=hp@axis.com \
/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).