From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard.Earnshaw@arm.com, gdb@sources.redhat.com,
Elena Zannoni <ezannoni@redhat.com>
Subject: Re: pseudo registers in the regcache
Date: Fri, 17 May 2002 09:31:00 -0000 [thread overview]
Message-ID: <200205171631.RAA21279@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 17 May 2002 12:22:39 EDT." <3CE52E4F.70009@cygnus.com>
> > How about renaming the 68k stuff as being MEMORY_REGS and reserving the
> > PSEUDO concept for what we really seem to want -- a view of a (or a
> > combination of) physical (or memory) register(s)?
>
> Or update mc68hc11 :-)
Well, I was hoping to avoid something that would be regarded as a majorly
invasive change (and which I've no chance of testing). Reclassifying the
mc68hc11 pseudos as memory registers would avoid that (basically it would
be a search and replace type operation ;-).
R
next prev parent reply other threads:[~2002-05-17 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 6:53 Richard Earnshaw
2002-05-17 9:22 ` Andrew Cagney
2002-05-17 9:31 ` Richard Earnshaw [this message]
2002-05-17 9:47 ` Andrew Cagney
2002-05-18 3:49 ` Richard Earnshaw
2002-05-18 11:08 ` 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=200205171631.RAA21279@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=ezannoni@redhat.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