From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Subject: [00/19] Eliminate some more current_gdbarch uses
Date: Fri, 05 Jun 2009 21:13:00 -0000 [thread overview]
Message-ID: <200906052113.n55LDMj4025990@d12av02.megacenter.de.ibm.com> (raw)
Hello,
this series of patches makes some more progress towards the goal of
eliminating the current_gdbarch global. This series tackles remaining
instances that are relatively simple to eliminate using existing
mechanism and relatively "local" changes.
While some patches in the series do change existing interfaces to
allow passing architecture information to some lower level, these
are typically less-frequently used ones that require only limited
changes to the rest of GDB.
After this patch series, the remaining instances of current_gdbarch
are difficult to eliminate, typically within frequently-called
central infrastructure routines. A follow-on patch series will
address those remaining occurrences.
This patch series was tested with no regressions on amd64-linux,
powerpc64-linux, spu-elf, s390-ibm-linux, and s390x-ibm-linux.
Also, I made sure an --enable-targets=all build still succeeds.
Comments welcome! I plan on committing the series within a week
or two (after I'm back from the GCC Summit).
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next reply other threads:[~2009-06-05 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 21:13 Ulrich Weigand [this message]
2009-06-05 22:24 ` Pedro Alves
2009-06-05 22:54 ` Tom Tromey
2009-06-05 23:30 ` Pedro Alves
2009-06-08 14:38 ` Ulrich Weigand
2009-06-08 14:48 ` Pedro Alves
2009-06-23 18:04 ` [rfc] longjmp breakpoints (Re: [00/19] Eliminate some more current_gdbarch uses) Ulrich Weigand
2009-06-24 15:02 ` Pedro Alves
2009-06-24 16:44 ` Ulrich Weigand
2009-06-17 18:58 ` [00/19] Eliminate some more current_gdbarch uses 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=200906052113.n55LDMj4025990@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