This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Example code: gdb pseudo-registers
- To: Michael Meissner <meissner at cygnus dot com>
- Subject: Re: Example code: gdb pseudo-registers
- From: Michael Snyder <msnyder at cygnus dot com>
- Date: Thu, 13 Jul 2000 09:21:08 -0700
- CC: Stan Shebs <shebs at apple dot com>, gdb-patches at sourceware dot cygnus dot com
- Organization: Cygnus Solutions
- References: <396D07F2.6892@cygnus.com> <396D2752.7EC33ECE@apple.com> <20000712235948.23654@cse.cygnus.com>
- Reply-To: msnyder at cygnus dot com
Michael Meissner wrote:
>
> On Wed, Jul 12, 2000 at 07:20:02PM -0700, Stan Shebs wrote:
> > Michael Snyder wrote:
> > >
> > > Here is an example of how you would use the pseudo-register feature.
> >
> > Good stuff! It occurs to me that although this is primarily an
> > implementor's feature, we should probably say *something* in the
> > manual? At the very least, user modification of a user-visible
> > register will cause other user-visible registers to magically
> > change, and we should document that this could happen, and that
> > the exact effects are arch-specific.
>
> I suspect port maintainers might want to go through and add pseudo registers
> for things like condition code registers that are packed into a single special
> purpos register. As a user, I would certainly welcome that.
That was another motivation for the work, yes.