From: Eli Zaretskii <eliz@gnu.org>
To: pgilliam@us.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [DOC PATCH] Re: [PATCH]*3 Re: [RFC] "info powerpc"
Date: Fri, 16 Sep 2005 10:26:00 -0000 [thread overview]
Message-ID: <umzmdmhq8.fsf@gnu.org> (raw)
In-Reply-To: <200509151206.19558.pgilliam@us.ibm.com> (message from Paul Gilliam on Thu, 15 Sep 2005 12:06:19 -0700)
> From: Paul Gilliam <pgilliam@us.ibm.com>
> Date: Thu, 15 Sep 2005 12:06:19 -0700
> Cc: gdb-patches@sources.redhat.com
>
> The "info powerpc" group of commands (all none of them) are not documented.
As you point out, "info powerpc" was until now a prefix with no
commands, that's why it is undocumented (or, rather, all zero of these
commands are documented ;-).
> If we decide to just get rid of it, then no user manual changes are needed.
Right; but your favorite alternative was to keep it.
> If we decide to keep it and make 'info powerpc altivec' an alias for "info vector", then we can use the attached doc patch.
Thanks; see a couple of comments below.
> 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
I don't think this is a good place for this section. There's already
a section on PowerPC-specific features, so we should add this
information there, I think.
> +@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
> +
I think this text should have a cross-reference to the "Vector Unit"
node, since the new command essentially does the same job, right?
Finally, we need a ChangeLog entry for this change.
Other than that, this patch for the manual is approved, assuming that
the code patches are also approved. Thanks.
next prev parent reply other threads:[~2005-09-16 10:26 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 ` [DOC PATCH] " Paul Gilliam
2005-09-16 10:26 ` Eli Zaretskii [this message]
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=umzmdmhq8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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