From: Paul Gilliam <pgilliam@us.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: [DOC PATCH] Re: [PATCH]*3 Re: [RFC] "info powerpc"
Date: Thu, 15 Sep 2005 19:06:00 -0000 [thread overview]
Message-ID: <200509151206.19558.pgilliam@us.ibm.com> (raw)
In-Reply-To: <u64t33syp.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
On Wednesday 14 September 2005 20:33, Eli Zaretskii wrote:
> > From: Paul Gilliam <pgilliam@us.ibm.com>
> > Date: Wed, 14 Sep 2005 17:10:39 -0700
> >
> > The second, 'altivec_alias.patch', functions like the first, except that infcmd.c is not touched. Instead, an 'info powerpc altivec' command
> > is added that turns itself into an alias for "info vector" the first time it's called. This can't be done with add_com_alias because the alias and
> > the command being aliased are on different command chains.
> >
> > The final patch, 'no_more_altivec.patch' depreciates the "info powerpc" command prefix and changes the testsuite to use "info vector". To make
> > this work, 'lookup_cmd_composition' in cli/cli-decode.c had to be changed so that a prefix command that has no sub-commands
> > can be depreciated.
>
> Please accompany any changes to user-visible behavior (such as new
> commands or changes in how existing command behave) with appropriate
> changes to the user manual. Thanks.
>
>
The "info powerpc" group of commands (all none of them) are not documented.
If we decide to just get rid of it, then no user manual changes are needed.
If we decide to keep it and make 'info powerpc altivec' an alias for "info vector", then we can use the attached doc patch.
[-- Attachment #2: doc.patch --]
[-- Type: text/x-diff, Size: 1482 bytes --]
? doc.patch
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.278
diff -a -u -r1.278 gdb.texinfo
--- gdb.texinfo 27 Aug 2005 12:51:28 -0000 1.278
+++ gdb.texinfo 15 Sep 2005 18:27:23 -0000
@@ -4991,6 +4991,7 @@
* Registers:: Registers
* Floating Point Hardware:: Floating point hardware
* Vector Unit:: Vector Unit
+* PowerPC Features:: PowerPC hardware features
* OS Information:: Auxiliary data provided by operating system
* Memory Region Attributes:: Memory region attributes
* Dump/Restore Files:: Copy between memory and a file
@@ -6247,6 +6248,22 @@
layout vary depending on the hardware.
@end table
+@node PowerPC Features
+@section PowerPC Features
+@cindex PowerPC Features
+
+Some PowerPC chips have features that are in addition to the core functionality
+of the architecture. Depending on the configuration, @value{GDBN} may be able
+to give you information about the status of those features.
+
+@table @code
+@kindex info powerpc altivec
+@item info powerpc altivec
+Display information about the Altivec unit. This will consist of the contents
+of the Altivec registers @code(vr0) through @code(vr31), along with that of the
+@code(vrsave) and @code(vsrc) registers.
+@end table
+
@node OS Information
@section Operating system auxiliary information
@cindex OS information
next prev parent reply other threads:[~2005-09-15 19:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 23:32 Paul Gilliam
2005-09-15 0:11 ` [PATCH]*3 " Paul Gilliam
2005-09-15 3:34 ` Eli Zaretskii
2005-09-15 19:06 ` Paul Gilliam [this message]
2005-09-16 10:26 ` [DOC PATCH] " Eli Zaretskii
2005-09-15 19:18 ` Mark Kettenis
2005-09-16 13:56 ` Daniel Jacobowitz
2005-09-16 17:45 ` Kevin Buettner
2005-09-16 18:51 ` Paul Gilliam
2005-09-16 19:40 ` Mark Kettenis
2005-09-16 19:47 ` Kevin Buettner
2005-09-19 17:50 ` [commit] "get rid of info powerpc" Paul Gilliam
2005-09-19 18:09 ` Daniel Jacobowitz
2005-09-20 20:05 ` Paul Gilliam
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=200509151206.19558.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=eliz@gnu.org \
--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