From: "Richard Guenther" <richard.guenther@gmail.com>
To: "Razya Ladelsky" <RAZYA@il.ibm.com>
Cc: gcc-patches@gcc.gnu.org, ctice@apple.com, gcc@gcc.gnu.org,
"Gerald Pfeifer" <gerald@pfeifer.com>,
"Janis Johnson" <janis187@us.ibm.com>,
"Mark Mitchell" <mark@codesourcery.com>,
stevenb.gcc@gmail.com,
"Kenneth Zadeck" <zadeck@naturalbridge.com>
Subject: Re: undocumented optimization options
Date: Mon, 12 Nov 2007 14:04:00 -0000 [thread overview]
Message-ID: <84fc9c000711120228v1043e0afg548e0a6cd666a7b3@mail.gmail.com> (raw)
In-Reply-To: <OF88AD2C7F.B27841FB-ONC2257391.0030F7C8-C2257391.0031DB12@il.ibm.com>
On Nov 12, 2007 10:06 AM, Razya Ladelsky <RAZYA@il.ibm.com> wrote:
> Kenneth Zadeck <zadeck@naturalbridge.com> wrote on 07/11/2007 19:49:29:
>
> > Razya Ladelsky wrote:
> > > Mark Mitchell <mark@codesourcery.com> wrote on 05/11/2007 01:51:33:
> > >
> > >
> > >> Gerald Pfeifer wrote:
> > >>
> > >>> On Thu, 1 Nov 2007, Janis Johnson wrote:
> > >>>
> > >>>> -fipa-cp steven
> > >>>> -fipa-matrix-reorg razya
> > >>>> -fipa-pure-const zadeck (enabled with -O)
> > >>>> -fipa-reference zadeck (enabled with -O)
> > >>>> -fipa-type-escape zadeck
> > >>>> -fvar-tracking-uninit ctice
> > >>>>
> > >>>>
> > >
> > > I'll add documentation for fipa-cp and fipa-matrix-reorg as soon as
> > > Zadeck commits his changes to invoke.texi.
> > >
> > > Thanks,
> > > Razya
> > >
> > >
>
> Hi,
>
> This patch adds documentation for fipa-cp and -fipa-matrix-reorg.
>
> 2007-11-12 Razya Ladelsky <razya@il.ibm.com>
>
> * doc/invoke.texi (fipa-cp, fipa-matrix-reorg): Add documentation.
>
> Ok to commit?
Please be more verbose. While people might have an idea what interprocedural
constant propagation is (though they probably don't immediately see that it
might increase code-size by versioning functions), certainly matrix flattening
deserves more comments.
Of course we might stay with the sparse documentation and just say in
addition "This optimization is experimental." to steer people away from it ;)
Richard.
For reference here's part of the patch:
@@ -5714,6 +5715,14 @@
@opindex fipa-pta
Perform interprocedural pointer analysis.
+@item -fipa-cp
+@opindex fipa-cp
+Perform interprocedural constant propagation.
+
+@item -fipa-matrix-reorg
+@opindex fipa-matrix-reorg
+Perform matrix flattening and transposing.
+
next prev parent reply other threads:[~2007-11-12 10:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 17:08 Janis Johnson
2007-11-03 17:22 ` Gerald Pfeifer
2007-11-05 3:32 ` Mark Mitchell
2007-11-07 17:48 ` Razya Ladelsky
2007-11-07 17:52 ` Kenneth Zadeck
2007-11-12 13:46 ` Razya Ladelsky
2007-11-12 14:04 ` Richard Guenther [this message]
2007-11-12 16:06 ` Razya Ladelsky
2007-11-12 16:07 ` Richard Guenther
2007-11-12 17:54 ` Mark Mitchell
2007-11-21 18:04 ` Razya Ladelsky
2007-11-21 20:56 ` Richard Guenther
2007-11-13 20:02 ` Ian Lance Taylor
2007-11-15 19:35 ` Razya Ladelsky
2007-11-03 20:41 ` Steven Bosscher
2007-11-03 22:28 ` Steven Bosscher
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=84fc9c000711120228v1043e0afg548e0a6cd666a7b3@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=RAZYA@il.ibm.com \
--cc=ctice@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=janis187@us.ibm.com \
--cc=mark@codesourcery.com \
--cc=stevenb.gcc@gmail.com \
--cc=zadeck@naturalbridge.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).