From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Subject: [rfc/rft] [0/5] Untangle register_addr et. al.
Date: Sat, 14 Apr 2007 21:08:00 -0000 [thread overview]
Message-ID: <200704142107.l3EL7SZn007059@d12av02.megacenter.de.ibm.com> (raw)
Hello,
the following series of 5 patches attempts to untangle everything related
to "traditional" ptrace-based register access. Overall, the patch set:
- Removes every definition of the global register_addr function.
- Removes most NM file definitions of KERNEL_U_SIZE, U_REGS_OFFSET,
KERNEL_U_ADDR, and REGISTER_U_ADDR (except on OSF and AIX).
- Removes all NM file definitions of CANNOT_STORE_REGISTER and
CANNOT_FETCH_REGISTER.
- Completely removes core-aout.c
- Adds a linux_trad_target () function to simplify use of traditional
register access in a Linux target.
- Gets rid of nearly all platform nm-linux.h files (except i386).
While not all portions of this are completely mechanical, the patch set
should not actually change the behaviour of any target (except core file
handling on alpha-linux, which should in fact improve ...).
However, as I don't have access to the majority of the affected native
targets, I'd appreciate any volunteers to test test patch set, in
particular on mips-linux and alpha-linux.
I'd also appreciate any comments on the patch set: is this the right
think to do at this point; am I overlooking anything here?
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next reply other threads:[~2007-04-14 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 21:08 Ulrich Weigand [this message]
2007-04-17 15:42 ` Daniel Jacobowitz
2007-04-23 15:44 ` 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=200704142107.l3EL7SZn007059@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.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