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>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: [rfc] [00/17] Get rid of current_gdbarch (4th)
Date: Thu, 11 Oct 2007 08:55:00 -0000 [thread overview]
Message-ID: <470DE48F.6020808@de.ibm.com> (raw)
Hi,
this is the 4th patch set for getting rid of current_gdbarch.
Patch 04/17 is a patch from Ulrich which adds "struct gdbarch" to "struct objfile" to enable accessing
an objfiles's architecture. Some of the following patches depend on this patch.
@Uli: I hope it's ok that I borrowed your patch ? ;-)
I do have no idea how to test the changes to win32-nat and go32-nat. Although the changes are still
mostly mechanical it would somewhen be a good idea to test it, I guess.
Tested by running testuite on x86 and gdb_mbuild.
Is this ok? Thanks a lot for your effort
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
next reply other threads:[~2007-10-11 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 8:55 Markus Deuling [this message]
2007-10-11 13:41 ` 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=470DE48F.6020808@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=drow@false.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