From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 00/10] Building the sim/ tree with clang
Date: Wed, 19 Oct 2022 16:24:39 +0100 [thread overview]
Message-ID: <cover.1666192979.git.aburgess@redhat.com> (raw)
The goal of this series is to allow the simulator tree to build using
clang.
The first 9 patches resolve some minor build warnings.
The last patch is where I give up (for now), and disable -Werror for 3
simulators which I think are going to be trickier to fix.
---
Andrew Burgess (10):
sim/sh: use fabs instead of abs
sim/ppc: don't try to print an uninitialized variable
sim/ppc: initialize a memory buffer in all cases
sim/ppc: don't pass uninitialized value to semctl for GETVAL calls
sim/ppc: fix for operator precedence warning from clang
sim/aarch64: remove two unused functions
sim/rx: delete an unused function
sim/h8300: avoid self assignment
sim/lm32: fix some missing function declaration warnings
sim/cris/m32c/sh: disable use of -Werror
sim/aarch64/simulator.c | 16 ----------------
sim/cris/Makefile.in | 3 +++
sim/h8300/compile.c | 4 ++--
sim/lm32/Makefile.in | 3 ---
sim/lm32/cpu.h | 11 +++++++++++
sim/lm32/dv-lm32cpu.c | 3 +++
sim/lm32/user.c | 3 +++
sim/m32c/Makefile.in | 3 +++
sim/ppc/altivec.igen | 2 +-
sim/ppc/emul_netbsd.c | 2 ++
sim/ppc/hw_sem.c | 4 ++--
sim/ppc/sim_calls.c | 5 +++--
sim/rx/rx.c | 8 --------
sim/sh/Makefile.in | 3 +++
sim/sh/interp.c | 2 +-
15 files changed, 37 insertions(+), 35 deletions(-)
--
2.25.4
next reply other threads:[~2022-10-19 15:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 15:24 Andrew Burgess [this message]
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 ` [PATCH 10/10] sim/cris/m32c/sh: disable use of -Werror Andrew Burgess
2022-10-20 3:53 ` 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=cover.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).