From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>, gdb@sources.redhat.com
Subject: Re: Register Groups (again)
Date: Mon, 19 Aug 2002 18:51:00 -0000 [thread overview]
Message-ID: <20020820015231.GA12252@nevyn.them.org> (raw)
In-Reply-To: <1020819185412.ZM21255@localhost.localdomain>
On Mon, Aug 19, 2002 at 11:54:12AM -0700, Kevin Buettner wrote:
> On Aug 18, 12:01am, Daniel Jacobowitz wrote:
>
> > On Sat, Aug 17, 2002 at 07:48:22PM -0400, Andrew Cagney wrote:
> > > See: http://sources.redhat.com/ml/gdb/2001-02/msg00268.html for the
> > > origins of this idea.
> > >
> > > I'd like to propose a new object ``struct reggroup'' and a number of
> > > methods:
> >
> > Hmm, it seems more intuitive to me to have attributes for each
> > register. Float, vector, system for the register's class or group, and
> > then we could have other not necessarily mutually exclusive flags.
> > Like, available in kernel or user mode.
>
> I think the attribute idea might be useful elsewhere, but for the
> purposes of being easily able to specify a register group for ``info
> registers'' (and other user interface uses), I think Andrew's
> proposal was fine.
I also agree.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-20 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 16:48 Andrew Cagney
2002-08-17 21:01 ` Daniel Jacobowitz
2002-08-17 22:45 ` Andrew Cagney
2002-08-18 7:44 ` Daniel Jacobowitz
2002-08-18 8:35 ` Andrew Cagney
2002-08-18 9:18 ` Daniel Jacobowitz
2002-08-19 11:54 ` Kevin Buettner
2002-08-19 18:51 ` Daniel Jacobowitz [this message]
2002-08-20 19:50 ` Andrew Cagney
2002-08-19 11:35 ` Kevin Buettner
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=20020820015231.GA12252@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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