From: Elena Zannoni <ezannoni@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard.Earnshaw@arm.com, Elena Zannoni <ezannoni@redhat.com>,
gdb@sources.redhat.com
Subject: Re: REGISTER_BYTE() and pseudos
Date: Wed, 15 May 2002 10:35:00 -0000 [thread overview]
Message-ID: <15586.40018.722458.418880@localhost.redhat.com> (raw)
In-Reply-To: <3CE29587.4070805@cygnus.com>
Andrew Cagney writes:
> > What should REGISTER_BYTE() return for a pseudo that doesn't have space
> > allocated in registers[]?
>
> It shouldn't matter. However, check with Elena for what was done with
> the sh5.
>
> Andrew
>
>
Yeah, I was going to chime in, but I am behind on this thread.
Richard, look at the sh-tdep.c file. I checked in the sh5 work. It
still needs another round of cleaning but ti should pretty much all be
there.
Elena
next prev parent reply other threads:[~2002-05-15 17:35 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 [this message]
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
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.40018.722458.418880@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