From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "Sandra Loosemore" <sandra@codesourcery.com>,
luoxhu <luoxhu@linux.ibm.com>, "Martin Jambor" <mjambor@suse.cz>,
"Xiong Hu Luo" <luoxhu@linux.vnet.ibm.com>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Segher Boessenkool" <segher@kernel.crashing.org>,
"Bill Schmidt" <wschmidt@linux.ibm.com>,
"Martin Liška" <mliska@suse.cz>
Subject: Re: [PATCH] Come up with ipa passes introduction in gccint documentation
Date: Wed, 09 Oct 2019 07:37:00 -0000 [thread overview]
Message-ID: <20191009072032.7svc64uqnbgllqiw@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAFiYyc3aFC_dq1vjj9bVqAEvc9weWXnuDohqMpaDH54e1RamWg@mail.gmail.com>
> On Tue, Oct 8, 2019 at 10:06 PM Sandra Loosemore
> <sandra@codesourcery.com> wrote:
> >
> > On 10/8/19 2:52 AM, luoxhu wrote:
> > > Hi,
> > >
> > > This is the formal documentation patch for IPA passes. Thanks.
> > >
> > >
> > > None of the IPA passes are documented in passes.texi. This patch adds
> > > a section IPA passes just before GIMPLE passes and RTL passes in
> > > Chapter 9 "Passes and Files of the Compiler". Also, a short description
> > > for each IPA pass is provided.
> > > gccint.pdf can be produced without errors.
> > >
> > > ChangeLog:
> > > PR middle-end/26241
> > > * doc/lto.texi (IPA): Reference to the IPA passes.
> > > * doc/passes.texi (Pass manager): Add node IPA passes and
> > > description for each IPA pass.
> >
> > Thanks for submitting this documentation patch! The content looks
> > helpful to me, but I see that it has quite a few grammar bugs (I
> > understand how hard English is even for native speakers....), plus some
> > issues like indexing, cross-referencing, use of jargon without defining
> > it, etc. I think it would be more efficient for me to take over
> > polishing the text some more than to mark it up for you to fix, but I'd
> > like to give others a few days to comment on technical content first.
>
> I think the contents are OK for a first try, so please go ahead polishing
> and commit. We can then improve the content as followup (I'm making
> a note for myself to not forget).
I will add some extra info once patch is in :)
Thanks for working on this!
Honza
>
> Thanks,
> Richard.
>
> > -Sandra
next prev parent reply other threads:[~2019-10-09 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 7:56 [RFC] " Xiong Hu Luo
2019-09-29 16:17 ` Segher Boessenkool
2019-09-30 1:47 ` luoxhu
2019-10-01 3:05 ` Segher Boessenkool
2019-09-30 8:32 ` Martin Jambor
2019-10-08 8:52 ` [PATCH] " luoxhu
2019-10-08 20:53 ` Sandra Loosemore
2019-10-09 7:20 ` Richard Biener
2019-10-09 7:37 ` Jan Hubicka [this message]
2019-10-10 19:57 ` Sandra Loosemore
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=20191009072032.7svc64uqnbgllqiw@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=luoxhu@linux.ibm.com \
--cc=luoxhu@linux.vnet.ibm.com \
--cc=mjambor@suse.cz \
--cc=mliska@suse.cz \
--cc=richard.guenther@gmail.com \
--cc=sandra@codesourcery.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).