From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
Joel Brobecker <brobecker@adacore.com>,
Daniel Jacobowitz <drow@false.org>,
Eli Zaretskii <eliz@gnu.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: [rfc] [00/15] Add gdbarch to register_name callback
Date: Wed, 31 Oct 2007 10:47:00 -0000 [thread overview]
Message-ID: <47285CC5.9020403@de.ibm.com> (raw)
Hi,
this is the next series of 15 patches. This patch set mainly adds gdbarch parameter to register_names gdbarch callback and all
callers in the various tdep-files.
The first two patches are for preparation. I merged together a lot of the trivial cases where gdbarch was just added to the various *_register_names
callbacks without changing anything else into patch 3.
All 15 patches depend on each other. Leaving one out at commit will break one or more targets.
Tested by building GDB with
alpha-elf ,-Werror
arm-elf ,-Werror
avr ,-Werror
cris-elf ,-Werror ,
frv-elf ,-Werror
h8300-elf ,-Werror
i386-elf ,-Werror
ia64-linux-gnu ,-Werror
m32c-elf ,-Werror
m32r-elf ,-Werror
m68hc11-elf ,-Werror ,
m68k-elf ,-Werror
m88k-openbsd ,-Werror
mep-elf ,-Werror
mips-elf ,-Werror
ms1-elf ,-Werror
hppa-elf ,-Werror
powerpc-eabi ,-Werror
s390-linux-gnu ,-Werror
score-elf
sh-elf ,-Werror
sh64-elf ,-Werror
sparc64-solaris2.10 ,-Werror
spu-elf ,-Werror
v850-elf ,-Werror
vax-netbsd ,-Werror
x86_64-linux-gnu ,-Werror
xstormy16-elf
xtensa-elf
Also tested by building and running testsuite native on x86, ppc/ppc64 and spu. I hope I covered any target.
Ok to commit?
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
next reply other threads:[~2007-10-31 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 10:47 Markus Deuling [this message]
2007-10-31 23:46 ` Ulrich Weigand
2007-11-01 8:30 ` Markus Deuling
2007-11-01 15:22 ` Ulrich Weigand
2007-11-02 8:09 ` Markus Deuling
2007-11-02 14:28 ` Ulrich Weigand
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=47285CC5.9020403@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=uweigand@de.ibm.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