Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Michael Snyder <msnyder@cygnus.com>,
	gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: [RFA] legacy_[read/write]_register_gen
Date: Tue, 29 Jan 2002 10:45:00 -0000	[thread overview]
Message-ID: <3C56EC48.8ACAC16B@redhat.com> (raw)
In-Reply-To: <3C5614AF.4050809@cygnus.com>

Andrew Cagney wrote:
> 
> > These two functions need to be able to read/write
> > a pseudo-register as well as a real register.
> >
> > 2002-01-28  Michael Snyder  <msnyder@redhat.com>
> >
> > * regcache.c (legacy_read_register_gen): Need to be able to
> >       read pseudo-register as well as real register.
> >       (legacy_write_register_gen): Ditto.
> 
> Michael,
> 
> When is this occuring?  Dig dig, I've a similar patch sitting in my
> sand-pit so, hmm, I've also seen it but don't remember why :-(
> 
> Andrew

Simplest case -- say you want to have a pseudo-register that
mirrors the contents of a real register.

static void
my_fetch_pseudo_register (int regnum)
{
  if (regnum == MY_MIRROR_REGNUM)
    {
	char buf[REGISTER_SIZE];
	regcache_read (MY_REAL_REGNUM, buf);
	regcache_write (MY_MIRROR_REGNUM, buf);
    }
}

You can't do that unles legacy_write_register_bytes can address
the regcache location of your pseudo-register.

> > Index: regcache.c
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/regcache.c,v
> > retrieving revision 1.30
> > diff -c -3 -p -r1.30 regcache.c
> > *** regcache.c        2002/01/15 02:06:46     1.30
> > --- regcache.c        2002/01/29 01:02:29
> > *************** legacy_read_register_gen (int regnum, ch
> > *** 310,316 ****
> >   void
> >   regcache_read (int rawnum, char *buf)
> >   {
> > !   gdb_assert (rawnum >= 0 && rawnum < NUM_REGS);
> >     /* For moment, just use underlying legacy code. Ulgh!!! */
> >     legacy_read_register_gen (rawnum, buf);
> >   }
> > --- 310,316 ----
> >   void
> >   regcache_read (int rawnum, char *buf)
> >   {
> > !   gdb_assert (rawnum >= 0 && rawnum < (NUM_REGS + NUM_PSEUDO_REGS));
> >     /* For moment, just use underlying legacy code. Ulgh!!! */
> >     legacy_read_register_gen (rawnum, buf);
> >   }
> > *************** legacy_write_register_gen (int regnum, c
> > *** 369,375 ****
> >   void
> >   regcache_write (int rawnum, char *buf)
> >   {
> > !   gdb_assert (rawnum >= 0 && rawnum < NUM_REGS);
> >     /* For moment, just use underlying legacy code. Ulgh!!! */
> >     legacy_write_register_gen (rawnum, buf);
> >   }
> > --- 369,375 ----
> >   void
> >   regcache_write (int rawnum, char *buf)
> >   {
> > !   gdb_assert (rawnum >= 0 && rawnum < (NUM_REGS + NUM_PSEUDO_REGS));
> >     /* For moment, just use underlying legacy code. Ulgh!!! */
> >     legacy_write_register_gen (rawnum, buf);
> >   }
> >
> >
> >


  reply	other threads:[~2002-01-29 18:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 17:09 Michael Snyder
2002-01-28 19:19 ` Andrew Cagney
2002-01-29 10:45   ` Michael Snyder [this message]
2002-01-29 11:22     ` Andrew Cagney
2002-01-29 11:31       ` Michael Snyder
2002-01-29 13:29         ` Andrew Cagney
2002-01-29 14:48           ` Michael Snyder

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=3C56EC48.8ACAC16B@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=cagney@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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