From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 6/9] sim: m32r: reduce -Wno-error scope
Date: Mon, 1 Nov 2021 00:59:42 -0400 [thread overview]
Message-ID: <20211101045945.23481-6-vapier@gentoo.org> (raw)
In-Reply-To: <20211101045945.23481-1-vapier@gentoo.org>
Only two files in here still generates warnings, so reduce the -Werror
disable to that now that we require GNU make and can set variables on
a per-object basis.
---
sim/m32r/Makefile.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sim/m32r/Makefile.in b/sim/m32r/Makefile.in
index 7b0ed1e0b932..d9d8acfc30fd 100644
--- a/sim/m32r/Makefile.in
+++ b/sim/m32r/Makefile.in
@@ -43,8 +43,8 @@ SIM_EXTRA_DEPS = \
SIM_EXTRA_CLEAN = m32r-clean
-# Code doesn't build cleanly yet.
-SIM_WERROR_CFLAGS =
+# Some modules don't build cleanly yet.
+cpu.o cpu2.o cpux.o m32r.o m32r2.o m32rx.o mloop.o mloop2.o mloopx.o sem.o sim-if.o traps.o: SIM_WERROR_CFLAGS =
## COMMON_POST_CONFIG_FRAG
--
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 ` Mike Frysinger [this message]
2021-11-01 4:59 ` [PATCH 7/9] sim: frv: " Mike Frysinger
2021-11-01 4:59 ` [PATCH 8/9] sim: lm32: " Mike Frysinger
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-6-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).