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, 13 Feb 2014 21:51:00 -0000 [thread overview]
Message-ID: <CAKxPW64f+cDvEP1Ucetzo91fXe=6oqkD5WzgG+hv37t5gWSk_Q@mail.gmail.com> (raw)
In-Reply-To: <CAKxPW67V8NEKQ8q4tjHGn3r5n53g4cuZ=SCGbK6Wi97EmCOb-g@mail.gmail.com>
Committed as r207767.
Indeed, I had an older version of makeinfo. Once I updated to the
latest version 5.2, I saw the warnings. Those are fixed by this patch.
Thanks,
Sharad
> On Tue, Feb 11, 2014 at 11:42 PM, Thomas Schwinge <thomas@codesourcery.com>
> wrote:
>>
>> Hi!
>>
>> On Wed, 5 Feb 2014 16:33:19 -0800, Sharad Singhai <singhai@google.com>
>> wrote:
>> > I am really sorry about the delay.
>>
>> No worries; not exactly a severe issue. ;-)
>>
>> > I couldn't exactly reproduce the
>> > warning which you described
>>
>> Maybe the version of makeinfo is relevant?
>>
>> $ makeinfo --version | head -n 1
>> makeinfo (GNU texinfo) 5.1
>>
>> > 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.
>>
>> Your patch does fix the problem; see the following diff of the build log,
>> where the warnings are now gone, and which also happens to contain the
>> makeinfo command line.
>>
>> @@ -4199,12 +4199,6 @@ if [ xinfo = xinfo ]; then \
>> makeinfo --split-size=5000000 --split-size=5000000
>> --no-split -I . -I ../../source/gcc/doc \
>> -I ../../source/gcc/doc/include -o doc/gccint.info
>> ../../source/gcc/doc/gccint.texi; \
>> fi
>> -../../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
>> if [ xinfo = xinfo ]; then \
>> makeinfo --split-size=5000000 --split-size=5000000
>> --no-split -I ../../source/gcc/doc \
>> -I ../../source/gcc/doc/include -o
>> doc/gccinstall.info ../../source/gcc/doc/install.texi; \
>>
>> > * doc/optinfo.texi: Fix order of nodes.
>>
>> Thanks, please commit.
>>
>>
>> Grüße,
>> Thomas
>
>
prev parent reply other threads:[~2014-02-13 21:51 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
2014-02-12 7:42 ` Thomas Schwinge
[not found] ` <CAKxPW67V8NEKQ8q4tjHGn3r5n53g4cuZ=SCGbK6Wi97EmCOb-g@mail.gmail.com>
2014-02-13 21:51 ` Sharad Singhai [this message]
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='CAKxPW64f+cDvEP1Ucetzo91fXe=6oqkD5WzgG+hv37t5gWSk_Q@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).