public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Stephane Carrez <Stephane.Carrez@france.sun.com>
To: nsd@redhat.com
Cc: gdb@sources.redhat.com, fnasser@redhat.com, insight@sources.redhat.com
Subject: Re: Register group proposal
Date: Wed, 21 Feb 2001 03:00:00 -0000	[thread overview]
Message-ID: <200102211100.MAA29081@sunchorus.France.Sun.COM> (raw)

Hi!

>
>On an architecture with a large register set, GDBtk's register window can
>be difficult to read and slow to update.  Users can customize the window
>to hide individual registers, but that's a tedious procedure.
>

Yes. It really makes sense.

For ChorusOS, we have this notion of 'grouping'.  The DebugAPI allows
to retrieve all registers of a given group.  Until now, we have defined
three groups (could define more):

 - general registers (ie, r0..r31, eax, ...)
 - floating point registers (ie, f0,...)
 - specific registers (ie, sprg0, dbat, cr0, ...)

In most cases, you are interested to look at general registers or floating
point regs.  Less often, you will need to display the specific registers.


It would be interesting then to take the 'grouping' into account by
the new/next register API. The current semantics of `to_fetch_registers()'
when a -1 is passed is to fetch all registers. You can see that as
a group of all registers. I think it's then necessary to clarify or
extend this semantics.

The goal is that if someone asks for the general registers, we don't
have to fetch the specific/floating point registers.

Well, this is very close to a previous discussion about optimizing
the fetch of registers within all GDB sources (frame, backtrace, locals, ...)

>
>The CLI "info registers" command already accepts a register name as an
>optional paramter.  It could be extended to try that parameter as a group
>name first and a register name second, so e.g. "info registers float"
>would display all floating-point registers.
>
>What do you think?
>
>Nick

It's great if a given platform could define its own groups of registers
and that they are recognized by Insight after that.

What about plugging the grouping in your regs_init_*() functions?

	Stephane

-	-	-	-	-	-	-	-	-	-
Stephane |Sun Microsystems			|
 Carrez	 |Network Service Provider Division	| http://www.sun.com
	 |6 avenue Gustave Eiffel		|
	 |F-78182, St-Quentin-en-Yvelines-Cedex |

email: Stephane.Carrez@France.Sun.COM


             reply	other threads:[~2001-02-21  3:00 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21  3:00 Stephane Carrez [this message]
2001-02-21  7:00 ` Nick Duffek
2001-02-21  9:34 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2001-02-28  1:59 Bernard Dautrevaux
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-27  8:53         ` Christopher Faylor
2001-02-27  9:57           ` Andrew Cagney
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-22  9:19 Michael Elizabeth Chastain
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 11:02           ` Kevin Buettner
2001-02-22 12:08             ` Andrew Cagney
2001-02-22  8:16     ` 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=200102211100.MAA29081@sunchorus.France.Sun.COM \
    --to=stephane.carrez@france.sun.com \
    --cc=fnasser@redhat.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).