From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: uweigand@de.ibm.com, deuling@de.ibm.com,
gdb-patches@sourceware.org, eliz@gnu.org, brobecker@adacore.com,
jimb@codesourcery.com, rearnsha@arm.com
Subject: Re: [rfc] [00/16] Get rid of current gdbarch
Date: Wed, 10 Oct 2007 12:01:00 -0000 [thread overview]
Message-ID: <20071010115352.GA10228@caradoc.them.org> (raw)
In-Reply-To: <200710100903.l9A93o9D018246@brahms.sibelius.xs4all.nl>
On Wed, Oct 10, 2007 at 11:03:50AM +0200, Mark Kettenis wrote:
> The solution here is (and always has been) making GDB's register
> number encoding a truly internal encoding. Then we could easily unify
> the different rs6000/powerpc variants. I understand that people want
> to keep the ability to talk to old stubs, so the remote target support
> code in GDB should take care of doing the conversion.
The patches I posted last week do this for PowerPC, in fact!
But there are places where we can't do it this way - at least not
without bigger changes. For instance, on MIPS the
dwarf2_reg_to_regnum method returns pseudo registers. The numbering
of pseudo registers starts at NUM_REGS, which varies depending on
the OS/ABI and on what target we end up connected to :-(
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-10 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 8:18 Markus Deuling
2007-10-08 13:03 ` Ulrich Weigand
2007-10-08 13:22 ` Markus Deuling
2007-10-08 13:35 ` Daniel Jacobowitz
2007-10-08 14:01 ` Ulrich Weigand
2007-10-08 14:10 ` Daniel Jacobowitz
2007-10-09 20:03 ` Ulrich Weigand
2007-10-09 21:39 ` Daniel Jacobowitz
2007-10-10 11:54 ` Mark Kettenis
2007-10-10 12:01 ` Daniel Jacobowitz [this message]
2007-10-08 13:16 ` Joel Brobecker
2007-10-09 7:02 ` Markus Deuling
2007-10-08 17:53 ` Maxim Grigoriev
2007-10-09 5:10 ` 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=20071010115352.GA10228@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=deuling@de.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
--cc=rearnsha@arm.com \
--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