From: Andrew Cagney <ac131313@ges.redhat.com>
To: gdb@sources.redhat.com
Subject: [rfc] New command ``info vector''
Date: Sat, 10 Aug 2002 11:58:00 -0000 [thread overview]
Message-ID: <3D556240.8090201@ges.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
Hello,
(following up a gdb-patches@ thread)
I'd like to propose a new command:
info vector
This command would display information about an architecture's vector
unit. Each architecture could customize it but, by default, it would
display any vector registers.
On the i386, for instance, it would display the xmm and mmx registers.
I've attached draft documentation.
thoughts?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1018 bytes --]
2002-08-10 Andrew Cagney <ac131313@redhat.com>
* gdbint.texinfo (Target Architecture Definition): Document
PRINT_VECTOR_INFO.
* gdb.texinfo (Vector Unit): Document "info vectors" command.
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.110
diff -u -r1.110 gdb.texinfo
--- doc/gdb.texinfo 10 Aug 2002 00:40:40 -0000 1.110
+++ doc/gdb.texinfo 10 Aug 2002 18:40:40 -0000
@@ -5583,6 +5583,20 @@
the ARM and x86 machines.
@end table
+@node Vector Unit
+@section Vector Unit
+@cindex vector unit
+
+Depending on the configuration, @value{GDBN} may be able to give you
+more information about the status of the vector unit.
+
+@table @code
+@kindex info vector
+@item info vector
+Display information about the vector unit. The exact contents and
+layout vary depending on the hardware.
+@end table
+
@node Memory Region Attributes
@section Memory region attributes
@cindex memory region attributes
next reply other threads:[~2002-08-10 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 11:58 Andrew Cagney [this message]
2002-08-11 6:56 ` Eli Zaretskii
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=3D556240.8090201@ges.redhat.com \
--to=ac131313@ges.redhat.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