This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [rfc] [00/16] Get rid of current gdbarch


> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]