Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
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, mark.kettenis@xs4all.nl
Subject: Re: [rfc] [00/16] Get rid of current gdbarch
Date: Wed, 10 Oct 2007 11:54:00 -0000	[thread overview]
Message-ID: <200710100903.l9A93o9D018246@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20071009200321.GA4564@caradoc.them.org> (message from Daniel 	Jacobowitz on Tue, 9 Oct 2007 16:03:21 -0400)

> Date: Tue, 9 Oct 2007 16:03:21 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Tue, Oct 09, 2007 at 09:59:39PM +0200, Ulrich Weigand wrote:
> > I agree that everything would be much easier if the register numbers
> > were constants.  But note that rs6000 is not the only platform where
> > this is not the case, I see the same (or even worse) also in mips,
> > m32c, xtensa, ...  (The mep usage also seems suspicious.)
> 
> Yes.  For some platforms (xtensa, mep) there may not be much we can
> do... and MIPS presents its own unique problems because of the use
> of pseudo registers for everything.  Hmm, this makes me wonder how
> deep the broken goes.  Maybe we shouldn't translate from DWARF numbers
> to internal ones until later.

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.

Mark


  reply	other threads:[~2007-10-10  9:07 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 [this message]
2007-10-10 12:01               ` Daniel Jacobowitz
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=200710100903.l9A93o9D018246@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.com \
    --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