From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 8/9] sim: lm32: reduce -Wno-error scope
Date: Mon, 1 Nov 2021 00:59:44 -0400 [thread overview]
Message-ID: <20211101045945.23481-8-vapier@gentoo.org> (raw)
In-Reply-To: <20211101045945.23481-1-vapier@gentoo.org>
Clean up some warnings in dv-lm32cpu, and all in sim-if, then reduce
the -Werror disable to the files that still aren't clean that now that
we require GNU make and can set variables on a per-object basis.
---
sim/lm32/Makefile.in | 4 ++--
sim/lm32/dv-lm32cpu.c | 2 +-
sim/lm32/sim-if.c | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/sim/lm32/Makefile.in b/sim/lm32/Makefile.in
index 2daf74d637bc..642c483acd26 100644
--- a/sim/lm32/Makefile.in
+++ b/sim/lm32/Makefile.in
@@ -24,8 +24,8 @@ SIM_EXTRA_DEPS = $(CGEN_INCLUDE_DEPS) $(srcdir)/../../opcodes/lm32-desc.h \
SIM_EXTRA_CLEAN = lm32-clean
-# Code doesn't build cleanly yet.
-SIM_WERROR_CFLAGS =
+# Some modules don't build cleanly yet.
+dv-lm32cpu.o mloop.o sem.o traps.o user.o: SIM_WERROR_CFLAGS =
## COMMON_POST_CONFIG_FRAG
diff --git a/sim/lm32/dv-lm32cpu.c b/sim/lm32/dv-lm32cpu.c
index 2f702bd72295..83fe6078b0b8 100644
--- a/sim/lm32/dv-lm32cpu.c
+++ b/sim/lm32/dv-lm32cpu.c
@@ -141,7 +141,7 @@ deliver_lm32cpu_interrupt (struct hw *me, void *data)
SIM_DESC sd = hw_system (me);
sim_cpu *cpu = STATE_CPU (sd, 0); /* NB: fix CPU 0. */
address_word cia = CPU_PC_GET (cpu);
- int interrupt = (int) data;
+ int interrupt = (uintptr_t) data;
HW_TRACE ((me, "interrupt-check event"));
diff --git a/sim/lm32/sim-if.c b/sim/lm32/sim-if.c
index f9143ea00375..2f8b3449917a 100644
--- a/sim/lm32/sim-if.c
+++ b/sim/lm32/sim-if.c
@@ -158,8 +158,8 @@ sim_open (SIM_OPEN_KIND kind, host_callback *callback, struct bfd *abfd,
free_state (sd);
return 0;
}
- /*sim_io_printf (sd, "Allocating memory at 0x%x size 0x%x\n", base, limit); */
- sim_do_commandf (sd, "memory region 0x%x,0x%x", base, limit);
+ /*sim_io_printf (sd, "Allocating memory at 0x%lx size 0x%lx\n", base, limit); */
+ sim_do_commandf (sd, "memory region 0x%lx,0x%lx", base, limit);
}
}
--
2.33.0
next prev parent reply other threads:[~2021-11-01 4:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 4:59 [PATCH 1/9] sim: or1k: build with -Werror Mike Frysinger
2021-11-01 4:59 ` [PATCH 2/9] sim: sh: reduce -Wno-error scope Mike Frysinger
2021-11-01 4:59 ` [PATCH 3/9] sim: cris: " Mike Frysinger
2021-11-01 4:59 ` [PATCH 4/9] sim: erc32: " Mike Frysinger
2021-11-01 4:59 ` [PATCH 5/9] sim: mips: " Mike Frysinger
2021-11-01 4:59 ` [PATCH 6/9] sim: m32r: " Mike Frysinger
2021-11-01 4:59 ` [PATCH 7/9] sim: frv: " Mike Frysinger
2021-11-01 4:59 ` Mike Frysinger [this message]
2021-11-01 4:59 ` [PATCH 9/9] sim: iq2000: " Mike Frysinger
2021-11-03 4:09 ` [PATCH 1/9] sim: or1k: build with -Werror Simon Marchi
2021-11-03 5:19 ` Mike Frysinger
2021-11-03 14:11 ` Simon Marchi
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=20211101045945.23481-8-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).