Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Don't include vector registers in ``info registers''
Date: Thu, 08 Aug 2002 18:45:00 -0000	[thread overview]
Message-ID: <3D531A59.96D86F43@redhat.com> (raw)
In-Reply-To: <20020809013343.GA5331@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> On Thu, Aug 08, 2002 at 07:51:57PM -0400, Andrew Cagney wrote:
> > Hello,
> >
> > The attached patch modifies the generic ``info registsters'' command so
> > that it precludes vector registers (in addition to floating-point
> > registers).  The online doco indicates:
> >
> > (gdb) help info registers
> > List of integer registers and their contents, for selected stack frame.
> > Register name as argument means describe only that register.
> > (gdb) help info all-registers
> > List of all registers and their contents, for selected stack frame.
> > Register name as argument means describe only that register.
> >
> > I think the change makes the behavour a better match for both the
> > documentation and what I think is the intent of the command.  Print a
> > minimal set of registers.
> >
> > It will eventually affect the i386 -- I've a patch to change the type of
> > xmm [and mmx] registers to true vectors.  When that is in, ``info
> > registers'' will stop displaying the xmm registers.
> >
> > Thoughts?
> 
> My only comment is that I would also like ``info registers'' not to
> print kernel-mode or processor status registers, since that seems (to
> me) to be appropriate; it should print registers for stack/pc and
> computation primarily, not things like the MSR.
> 
> Might be harder to do generically though.

That would mean that in order to see things like the status and
control registers, you would have to do info all-reg, which would
then spit out all your FP and VEC registers too.  Folks who need
the in-between registers might not like that.


  reply	other threads:[~2002-08-09  1:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 16:52 Andrew Cagney
2002-08-08 17:07 ` Andrew Cagney
2002-08-08 19:07   ` Elena Zannoni
2002-08-08 19:24     ` Andrew Cagney
2002-08-13 14:45     ` Andrew Cagney
2002-08-09 11:39   ` Andrew Cagney
2002-08-15 17:12   ` Andrew Cagney
2002-08-08 18:33 ` Daniel Jacobowitz
2002-08-08 18:45   ` Michael Snyder [this message]
2002-08-08 19:35   ` Andrew Cagney
2002-08-08 18:50 ` Michael Snyder

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=3D531A59.96D86F43@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@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