Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Register Groups (again)
Date: Sat, 17 Aug 2002 22:45:00 -0000	[thread overview]
Message-ID: <3D5F3484.8010807@ges.redhat.com> (raw)
In-Reply-To: <20020818040145.GA26488@nevyn.them.org>

> 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.
> 
> Just a thought though.

Sorry, I think I'm missing something.  I don't see a difference. 
s/reggroup/regattrib/?

>> - how it relates to frames
>> 
>> It currently assumes that the register groups are identical between 
>> frames :-/

i.e.:
	register_reggroup_p(gdbarch,regnum,group)
rather than:
	frame_register_reggroup_p(frame,regnum,group)

> With an attribute scheme, once we know which registers are present in a
> frame we'd know which (say) float registers are present in that
> frame...

Now I'm really confused.  How is this not possible using what I described?

Andrew



  reply	other threads:[~2002-08-18  5:45 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 [this message]
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
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=3D5F3484.8010807@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=drow@mvista.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