Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Elena Zannoni <ezannoni@redhat.com>,
	Andrew Cagney <ac131313@cygnus.com>,
	gdb@sources.redhat.com
Subject: Re: REGISTER_BYTE() and pseudos
Date: Wed, 15 May 2002 11:45:00 -0000	[thread overview]
Message-ID: <15586.44161.56803.886450@localhost.redhat.com> (raw)
In-Reply-To: <200205151807.TAA18580@cam-mail2.cambridge.arm.com>

Richard Earnshaw writes:
 > OK, I see what you are doing.  Basically, if a pseudo maps onto a real 
 > register somewhere in the regcache, you return the address of that.
 > 
 > However, what should be done if the pseudo doesn't exist as a single 
 > entry, or if it is a manipulation of a real register?  For example, on the 
 > ARM, the CPSR may be just a few bits retrieved from the PC.
 > 
 > Also, what would you do if you needed to address two non-adjacent 
 > registers?
 > 
 > R.

Look at sh64_pseudo_register_read() and how FPSCR is treated.  FPSCR
is built as a collection of non-adjacent bits in various architectural
registers.

In theory sh64_pseudo_register_read shouldn't even be there.  All that
code should just be part of sh64_register_read.  Basically
sh64_register_read just does what it wants with the registers, almost
like if there was no difference between pseudos and real registers.

Same with sh64_register_write and sh64_pseudo_register_write.

Elena


  reply	other threads:[~2002-05-15 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15  9:36 Richard Earnshaw
2002-05-15 10:06 ` Andrew Cagney
2002-05-15 10:35   ` Elena Zannoni
2002-05-15 10:46     ` Richard Earnshaw
2002-05-15 11:46       ` Elena Zannoni
2002-05-15 11:08     ` Richard Earnshaw
2002-05-15 11:45       ` Elena Zannoni [this message]
2002-05-15 13:01       ` 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=15586.44161.56803.886450@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@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