From: Andrew Cagney <ac131313@cygnus.com>
To: Nick Duffek <nsd@redhat.com>
Cc: gdb@sources.redhat.com, insight@sources.redhat.com
Subject: Re: Register group proposal
Date: Thu, 22 Feb 2001 08:16:00 -0000 [thread overview]
Message-ID: <3A953AE8.3EFB6CE4@cygnus.com> (raw)
In-Reply-To: <200102221326.f1MDQJc02778@rtl.cygnus.com>
Nick Duffek wrote:
> >Even if it isn't made an object could I suggest the convention of a
> >...._REGGROUP() be adopted to all methods that return a register group.
>
> Yes, that's helpful for supporting Stephane's idea of using register
> groups for purposes other than display, e.g. fetching and storing.
Just FYI,
Since REGGROUP is bound to a frame and _not_ the raw register cache, it
wouldn't be directly applicable to what Stephane was suggesting.
For an existing example of this unfortunate confusion of layers (and how
it goes wrong) have a look at RAW_REGISTER_BYTES() and how code much of
the code manipulating a frame's cooked/pseudo registers (incorrectly)
uses it.
enjoy,
Andrew
next prev parent reply other threads:[~2001-02-22 8:16 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 20:56 Nick Duffek
2001-02-21 6:44 ` Fernando Nasser
2001-02-21 7:10 ` Nick Duffek
2001-02-21 7:36 ` Fernando Nasser
2001-02-21 7:58 ` Keith Seitz
2001-02-21 8:50 ` Andrew Cagney
2001-02-21 11:43 ` Andrew Cagney
2001-02-25 15:36 ` Nick Duffek
2001-02-21 11:43 ` Andrew Cagney
2001-02-21 12:28 ` Andrew Cagney
2001-02-21 12:18 ` Andrew Cagney
2001-02-22 0:59 ` Eli Zaretskii
2001-02-22 4:29 ` Nick Duffek
2001-02-22 8:46 ` Andrew Cagney
2001-02-22 8:56 ` Keith Seitz
2001-02-22 9:20 ` Andrew Cagney
2001-02-22 5:17 ` Nick Duffek
2001-02-22 6:36 ` Fernando Nasser
2001-02-22 8:23 ` Andrew Cagney
2001-02-22 7:58 ` Andrew Cagney
2001-02-22 8:37 ` Nick Duffek
2001-02-22 9:12 ` Andrew Cagney
2001-02-22 10:15 ` Nick Duffek
2001-02-22 10:25 ` Andrew Cagney
2001-02-22 11:40 ` Eli Zaretskii
2001-02-22 8:16 ` Andrew Cagney [this message]
2001-02-21 3:00 Stephane Carrez
2001-02-21 7:00 ` Nick Duffek
2001-02-21 9:34 ` Andrew Cagney
2001-02-22 9:19 Michael Elizabeth Chastain
2001-02-23 2:52 Bernard Dautrevaux
2001-02-24 15:43 ` Nick Duffek
2001-02-26 18:21 ` Andrew Cagney
2001-02-27 10:30 ` Jim Kleck
2001-02-27 11:24 ` Per Bothner
2001-02-27 13:44 ` Jim Kleck
2001-02-27 15:17 ` Andrew Cagney
2001-02-26 5:29 Bernard Dautrevaux
2001-02-26 9:28 ` Christopher Faylor
2001-02-26 10:56 ` Andrew Cagney
2001-02-26 11:28 ` Christopher Faylor
2001-02-26 17:02 ` Andrew Cagney
2001-02-28 1:59 Bernard Dautrevaux
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=3A953AE8.3EFB6CE4@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=nsd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).