From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>,
Ulrich Weigand <uweigand@de.ibm.com>
Subject: [rfc] [00/12] Get rid of current_gdbarch
Date: Fri, 03 Aug 2007 12:11:00 -0000 [thread overview]
Message-ID: <46B31B13.4020304@de.ibm.com> (raw)
Hi,
this and the next patch sets are another step in the direction of per-frame architecture. To achieve that
goal GDB needs to get rid of the global variable current_gdbarch. This set of 12 patches replaces (trivial to
replace occurences of) current_gdbarch by appropriate methods like get_frame_arch or get_regcache_arch etc.
Currently get_frame_arch just returns current_gdbarch but this will be replaced by later patches.
I tested this patch set on x86 (native and remote), ppc and ppc64 by compiling and running the testsuite. I also did a gdb_mbuild with all
targets to make sure it compiles.
Some later patches will be non-trivial and hard for me to test due to lack of those machines. It would be great if
some of you could test patches for different archs like mips, arm, etc. but this will still take a while.
This patch set replaces some of the current_gdbarch's in following files:
* aix-thread.c
* arm-tdep.c
* alpha-{linux-nat,nat,tdep}.c
* frame.c
* i386-tdep.c
* mips-tdep.c
* ppc-linux-nat.c
* rs6000-tdep.c
* sh[64]-tdep.c
* xtensa-tdep.c
* remote.c
Is this ok?
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
next reply other threads:[~2007-08-03 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 12:11 Markus Deuling [this message]
2007-08-03 19:38 ` Jim Blandy
2007-08-05 6:55 ` Joel Brobecker
2007-08-06 7:50 ` Markus Deuling
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=46B31B13.4020304@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--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