This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: pseudo registers in the regcache
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Richard dot Earnshaw at arm dot com
- Cc: gdb at sources dot redhat dot com, Elena Zannoni <ezannoni at redhat dot com>
- Date: Fri, 17 May 2002 12:48:03 -0400
- Subject: Re: pseudo registers in the regcache
- References: <200205171631.RAA21279@cam-mail2.cambridge.arm.com>
> How about renaming the 68k stuff as being MEMORY_REGS and reserving the
>> > PSEUDO concept for what we really seem to want -- a view of a (or a
>> > combination of) physical (or memory) register(s)?
>
>>
>> Or update mc68hc11 :-)
>
>
> Well, I was hoping to avoid something that would be regarded as a majorly
> invasive change (and which I've no chance of testing). Reclassifying the
> mc68hc11 pseudos as memory registers would avoid that (basically it would
> be a search and replace type operation ;-).
I'd rather not see GDB do anything to legitimatize a now redundant
mechanism.
I think the line-in-sand approach to just banning values in
pseudo-registers post register-read is both better and easier
Shouldn't be too hard to do this using the tweaked regcache - that uses
regcache->descr->nr_registers instead of NUM_REGS + NUM_PSEUDO_REGS. In
fact [evil laughter :-)] I can think of a few other things that it could
disallow:
- holes in the register cache
- differing register virtual and raw sizes
- ...
(but worry about that later :-)
enjoy,
Andrew