Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Klee Dienes <klee@apple.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Print vector registers in natural format, not hex
Date: Mon, 21 Oct 2002 17:23:00 -0000	[thread overview]
Message-ID: <3DB49A9A.9080706@redhat.com> (raw)
In-Reply-To: <22199F8A-DD36-11D6-B6D6-00039396EEB8@apple.com>

> Eli Zaretskii <eliz@is.elta.co.il> writes:
> 
>> Thanks, this is approved.
>> 
>> Do we have facilities for printing vector registers?  If so, we should
>> probably add a cross-reference to their description here.  The
>> intersted reader will most probably wonder what can she do to print
>> vector registers when she reads these passages.

> 
> The closest facility is the 'info vector' command, which by default prints the contents of all vector registers, but is documented simply as "Print the status of the vector unit.", which I take to mean that it can be overridden to have arch-specific output, much like 'info float'.  An 'info vector-registers' and 'info fp-registers' command might not be such a bad idea, but none exists at the moment that I know of.

The wording was lifted from ``info float''.  The assumption is that the 
architecture backend will eventually find it necessary customize these 
commands.  For the architectures I've looked at (Intel's SSE and WMMX) 
an ``info vector'' command ends up needing to print both true vector 
registers and some associated status registers.  The (er now legendary) 
reggroups code addresses much of this problem.

I don't think we need ``info fp-registers'' or ``info vector-registers'' 
commands.

Andrew



  parent reply	other threads:[~2002-10-22  0:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 13:41 Klee Dienes
2002-10-04 13:52 ` Daniel Jacobowitz
2002-10-04 14:11   ` Klee Dienes
2002-10-04 14:36     ` Daniel Jacobowitz
2002-10-18 16:23       ` Elena Zannoni
2002-11-04 20:02         ` Klee Dienes
2002-11-04 20:34           ` Daniel Jacobowitz
2002-10-05 10:29 ` Eli Zaretskii
2002-10-05 13:03   ` Klee Dienes
2002-10-06 11:31     ` Eli Zaretskii
2002-10-11  9:26       ` Klee Dienes
2002-10-12  2:01         ` Eli Zaretskii
2002-10-21 17:23         ` Andrew Cagney [this message]
2002-10-18 16:37 ` Elena Zannoni
2002-11-05  0:48   ` Klee Dienes

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=3DB49A9A.9080706@redhat.com \
    --to=ac131313@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=klee@apple.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