From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 10/10] sim/cris/m32c/sh: disable use of -Werror
Date: Wed, 19 Oct 2022 16:24:49 +0100 [thread overview]
Message-ID: <42c09bcd56bb7bf0a84d58ffad71894f284b5401.1666192979.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1666192979.git.aburgess@redhat.com>
When building the cris, m32c, and sh simulators with Clang I am seeing
build warnings from a few objects. These three simulators currently
build with -Werror, and so these warnings cause the build to fail.
When built with gcc I don't see any warnings from these targets, so
the -Werror is fine.
As the warnings are not new, in this commit, I propose that we disable
the use of -Werror for these three simulators. With this done it is
now possible to build the complete simulator tree using clang.
---
sim/cris/Makefile.in | 3 +++
sim/m32c/Makefile.in | 3 +++
sim/sh/Makefile.in | 3 +++
3 files changed, 9 insertions(+)
diff --git a/sim/cris/Makefile.in b/sim/cris/Makefile.in
index d58aeee9363..53e485dca02 100644
--- a/sim/cris/Makefile.in
+++ b/sim/cris/Makefile.in
@@ -41,6 +41,9 @@ SIM_EXTRA_DEPS = \
SIM_EXTRA_CLEAN = cris-clean
+# Some modules don't build cleanly yet.
+mloopv10f.o mloopv32f.o: SIM_WERROR_CFLAGS =
+
## COMMON_POST_CONFIG_FRAG
arch = cris
diff --git a/sim/m32c/Makefile.in b/sim/m32c/Makefile.in
index 2436eb940f4..dd9b3aaf175 100644
--- a/sim/m32c/Makefile.in
+++ b/sim/m32c/Makefile.in
@@ -40,4 +40,7 @@ SIM_OBJS = \
trace.o \
$(ENDLIST)
+# Some modules don't build cleanly yet.
+mem.o: SIM_WERROR_CFLAGS =
+
## COMMON_POST_CONFIG_FRAG
diff --git a/sim/sh/Makefile.in b/sim/sh/Makefile.in
index fc794f30687..a496095e767 100644
--- a/sim/sh/Makefile.in
+++ b/sim/sh/Makefile.in
@@ -24,4 +24,7 @@ SIM_OBJS = \
SIM_EXTRA_LIBS = -lm
SIM_EXTRA_DEPS = table.c code.c ppi.c
+# Some modules don't build cleanly yet.
+interp.o: SIM_WERROR_CFLAGS =
+
## COMMON_POST_CONFIG_FRAG
--
2.25.4
next prev parent reply other threads:[~2022-10-19 15:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 15:24 [PATCH 00/10] Building the sim/ tree with clang Andrew Burgess
2022-10-19 15:24 ` [PATCH 01/10] sim/sh: use fabs instead of abs Andrew Burgess
2022-10-23 13:53 ` Mike Frysinger
2022-10-24 16:05 ` Andrew Burgess
2022-10-19 15:24 ` [PATCH 02/10] sim/ppc: don't try to print an uninitialized variable Andrew Burgess
2022-10-23 13:51 ` Mike Frysinger
2022-10-24 16:05 ` Andrew Burgess
2022-10-19 15:24 ` [PATCH 03/10] sim/ppc: initialize a memory buffer in all cases Andrew Burgess
2022-10-23 13:50 ` Mike Frysinger
2022-10-24 16:25 ` Andrew Burgess
2022-10-19 15:24 ` [PATCH 04/10] sim/ppc: don't pass uninitialized value to semctl for GETVAL calls Andrew Burgess
2022-10-23 14:01 ` Mike Frysinger
2022-10-19 15:24 ` [PATCH 05/10] sim/ppc: fix for operator precedence warning from clang Andrew Burgess
2022-10-23 13:55 ` Mike Frysinger
2022-10-24 16:26 ` Andrew Burgess
2022-10-19 15:24 ` [PATCH 06/10] sim/aarch64: remove two unused functions Andrew Burgess
2022-10-23 13:55 ` Mike Frysinger
2022-10-24 16:26 ` Andrew Burgess
2022-10-19 15:24 ` [PATCH 07/10] sim/rx: delete an unused function Andrew Burgess
2022-10-23 13:54 ` Mike Frysinger
2022-10-19 15:24 ` [PATCH 08/10] sim/h8300: avoid self assignment Andrew Burgess
2022-10-23 13:52 ` Mike Frysinger
2022-10-24 16:26 ` Andrew Burgess
2022-10-19 15:24 ` [PATCH 09/10] sim/lm32: fix some missing function declaration warnings Andrew Burgess
2022-10-23 14:13 ` Mike Frysinger
2022-10-24 16:27 ` Andrew Burgess
2022-10-19 15:24 ` Andrew Burgess [this message]
2022-10-20 3:53 ` [PATCH 10/10] sim/cris/m32c/sh: disable use of -Werror Tsukasa OI
2022-10-21 15:58 ` Andrew Burgess
2022-10-24 8:58 ` Tsukasa OI
2022-10-24 16:23 ` Andrew Burgess
2022-10-20 18:36 ` Tom Tromey
2022-10-23 14:17 ` Mike Frysinger
2022-10-20 18:36 ` [PATCH 00/10] Building the sim/ tree with clang Tom Tromey
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=42c09bcd56bb7bf0a84d58ffad71894f284b5401.1666192979.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--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).