Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/rfa:sh] gdbarch_register_read() -> gdbarch_cooked_register_read()
Date: Thu, 25 Jul 2002 12:51:00 -0000	[thread overview]
Message-ID: <3D404E63.2090209@ges.redhat.com> (raw)
In-Reply-To: <15680.18245.941961.80077@localhost.redhat.com>

>  >  > One NB.  The parameter set is technically redundant.  The assertion:
>  >  > 
>  >  > 	gdbarch == regcache_gdbarch (regcache)
>  >  > 
>  >  > always holds so the gdbarch parameter isn't strictly needed.  I figured 
>  >  > that it is more convenient to include the gdbarch as a parameter and 
>  >  > save everyone the hassle of including the above line in their *-tdep code.
>  >  > 
>  >  > The SH stuff should be reviewed.  I think its on the right track since 
>  >  > sh-tdep.c no longer refers to current_regcache!!!
>  >  > 
> 
> 
> So, wait a minute, is the sh the only port that overwrites the generic
> register reads and writes to handle pseudo registers?

Gnew speak: s/pseudo/cooked/.  Pseudo registers are implemented 
differently :-)

In GDB (i.e. the official GDB sources)? Yes.

The only architecture using the gdbarch register read/write (i.e. the 
new cooked interface) is the SH.

The only platform using the old fetch/store pseudo register interface is 
the m68hc11.  The conversion looks easy.

The MIPS is the platform that desperatly needs to start using cooked 
registers.  The Arm is waiting, ready to pounce, when all the changes 
are in.

enjoy,
Andrew



  reply	other threads:[~2002-07-25 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24 16:47 Andrew Cagney
2002-07-25  6:57 ` Elena Zannoni
2002-07-25 12:15   ` Elena Zannoni
2002-07-25 12:51     ` Andrew Cagney [this message]
2002-07-25 13:11       ` Elena Zannoni
2002-07-30  7:18 ` Andrew Cagney

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=3D404E63.2090209@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.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