From: Martin Jambor <mjambor@suse.cz>
To: Xiong Hu Luo <luoxhu@linux.vnet.ibm.com>, gcc-patches@gcc.gnu.org
Cc: segher@kernel.crashing.org, wschmidt@linux.ibm.com,
luoxhu@linux.ibm.com, hubicka@ucw.cz, mliska@suse.cz,
Xiong Hu Luo <luoxhu@linux.vnet.ibm.com>
Subject: Re: [RFC] Come up with ipa passes introduction in gccint documentation
Date: Mon, 30 Sep 2019 08:32:00 -0000 [thread overview]
Message-ID: <ri6muem2nha.fsf@suse.cz> (raw)
In-Reply-To: <20190929075637.79741-1-luoxhu@linux.vnet.ibm.com>
Hi,
I agree that we should have a chapter on IPA passes in gccint, just
please note that...
On Sun, Sep 29 2019, Xiong Hu Luo wrote:
> There is no ipa passes introduction in gccint now, is it nessessary to
> add this part as both GIMPLE passes and RTL passes breif intruduction
> already exit in Chapter 9 "Passes and Files of the Compiler" but no
> section for ipa passes?
> If it's OK, this is just a framework, lots of words need be filled into
> each item.
>
> ChangeLog:
> * doc/lto.texi (IPA): Reference to the IPA passes.
> * doc/passes.texi (Tree SSA passes): Add node IPA passes.
> ---
> gcc/doc/lto.texi | 6 ++---
> gcc/doc/passes.texi | 62 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 65 insertions(+), 3 deletions(-)
>
...
> diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi
> index 6edb9a0bfb7..0b6cf73469c 100644
> --- a/gcc/doc/passes.texi
> +++ b/gcc/doc/passes.texi
> @@ -21,6 +21,7 @@ where near complete.
> * Gimplification pass:: The bits are turned into something we can optimize.
> * Pass manager:: Sequencing the optimization passes.
> * Tree SSA passes:: Optimizations on a high-level representation.
> +* IPA passes:: Optimizations on scope of intra-procedual.
...IPA stands for inter (not intra!) procedural analysis.
Martin
next prev parent reply other threads:[~2019-09-30 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 7:56 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 [this message]
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
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=ri6muem2nha.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=luoxhu@linux.ibm.com \
--cc=luoxhu@linux.vnet.ibm.com \
--cc=mliska@suse.cz \
--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).