From: Sharad Singhai <singhai@google.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Documentation for dump and optinfo output
Date: Thu, 06 Feb 2014 00:34:00 -0000 [thread overview]
Message-ID: <CAKxPW671KgBCJoYnRHiDj5fccqEhB6X0pEq48gjvJxnT_Fb-Rw@mail.gmail.com> (raw)
In-Reply-To: <87d2jh7kah.fsf@kepler.schwinge.homeip.net>
I am really sorry about the delay. I couldn't exactly reproduce the
warning which you described, but I found a place where two nodes were
out of order in optinfo.texi. Could you please apply the following
patch and see if the problem goes away? If it works for you, I will
commit the doc fixes.
Also I would appreciate the exact command which produces these warnings.
Thanks,
Sharad
2014-02-05 Sharad Singhai <singhai@google.com>
* doc/optinfo.texi: Fix order of nodes.
Index: doc/optinfo.texi
===================================================================
--- doc/optinfo.texi (revision 207525)
+++ doc/optinfo.texi (working copy)
@@ -12,8 +12,8 @@ information about various compiler transformations
@menu
* Dump setup:: Setup of optimization dumps.
* Optimization groups:: Groups made up of optimization passes.
+* Dump files and streams:: Dump output file names and streams.
* Dump output verbosity:: How much information to dump.
-* Dump files and streams:: Dump output file names and streams.
* Dump types:: Various types of dump functions.
* Dump examples:: Sample usage.
@end menu
Thanks,
Sharad
On Fri, Jan 24, 2014 at 2:20 AM, Thomas Schwinge
<thomas@codesourcery.com> wrote:
> Hi!
>
> On Thu, 19 Dec 2013 01:44:08 -0800, Sharad Singhai <singhai@google.com> wrote:
>> I ran 'make doc' and browsed the info output for basic sanity. Okay for trunk?
>
>> * Makefile.in: Add optinfo.texi.
>> * doc/optinfo.texi: New documentation for optimization info.
>> * doc/passes.texi: Add new node.
>
> Thanks for contributing to the documentation!
>
> During build, I'm seeing the following warnings; would be great if you
> could address these:
>
> ../../source/gcc/doc/optinfo.texi:45: warning: node next `Optimization groups' in menu `Dump output verbosity' and in sectioning `Dump files and streams' differ
> ../../source/gcc/doc/optinfo.texi:77: warning: node next `Dump files and streams' in menu `Dump types' and in sectioning `Dump output verbosity' differ
> ../../source/gcc/doc/optinfo.texi:77: warning: node prev `Dump files and streams' in menu `Dump output verbosity' and in sectioning `Optimization groups' differ
> ../../source/gcc/doc/optinfo.texi:104: warning: node next `Dump output verbosity' in menu `Dump files and streams' and in sectioning `Dump types' differ
> ../../source/gcc/doc/optinfo.texi:104: warning: node prev `Dump output verbosity' in menu `Optimization groups' and in sectioning `Dump files and streams' differ
> ../../source/gcc/doc/optinfo.texi:137: warning: node prev `Dump types' in menu `Dump files and streams' and in sectioning `Dump output verbosity' differ
>
>
> Grüße,
> Thomas
next prev parent reply other threads:[~2014-02-06 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 9:44 Sharad Singhai
2013-12-19 9:59 ` Richard Biener
2014-01-24 10:21 ` Thomas Schwinge
2014-02-06 0:34 ` Sharad Singhai [this message]
2014-02-12 7:42 ` Thomas Schwinge
[not found] ` <CAKxPW67V8NEKQ8q4tjHGn3r5n53g4cuZ=SCGbK6Wi97EmCOb-g@mail.gmail.com>
2014-02-13 21:51 ` Sharad Singhai
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=CAKxPW671KgBCJoYnRHiDj5fccqEhB6X0pEq48gjvJxnT_Fb-Rw@mail.gmail.com \
--to=singhai@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).