From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: janis187@us.ibm.com, gcc-patches <gcc-patches@gcc.gnu.org>,
gerald@pfeifer.com, jsm@polyomino.org.uk
Subject: Re: undocumented optimization options
Date: Thu, 08 Nov 2007 13:48:00 -0000 [thread overview]
Message-ID: <473313A6.2050102@naturalbridge.com> (raw)
In-Reply-To: <84fc9c000711080107y688f09ccqb7ff64307c9425f6@mail.gmail.com>
Richard Guenther wrote:
> On 11/5/07, Kenneth Zadeck <zadeck@naturalbridge.com> wrote:
>
>> Janis Johnson wrote:
>>
>>> Several options reported by --help=optimize are not documented in the
>>> GCC Manual (via invoke.texi) but are still reported with
>>> --help=optimize,^undocumented. Here are the options along with the
>>> people who checked in the entries to common.opt:
>>>
>>> -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
>>>
>>> Is there a policy about whether an experimental option can be left
>>> undocumented, or should it be documented with a statement that it is
>>> experimental?
>>>
>>> If an option is left undocumented on purpose then its entry in common.opt
>>> should include "Undocumented".
>>>
>>> Janis
>>>
>>>
>>>
>>>
>> This patch gets me off of janis's bad list (or at least the one
>> associated with undocumented options). As directed by diego, I sorted
>> the option lists for -O, -Os and -O2 since this had rotted.
>>
>> 2007-11-05 Kenneth Zadeck <zadeck@naturalbridge.com>
>>
>> * common.opt: Add pointer to doc/options.texi.
>> * doc/invoke.texi (-fdse, -fdce, -fauto-inc-dec, -fipa-pure-const,
>> -fipa-reference): Add or correct doc. Sorted options list for -Os
>> -O, -O2.
>>
>> Ok to commit?
>>
>
> Ok, thanks.
> Richard.
>
>
>> Kenny
>>
>>
>>
>>
committed as revision 130000
kenny
next prev parent reply other threads:[~2007-11-08 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1193936896.7293.7.camel@janis-laptop>
2007-11-05 20:04 ` Kenneth Zadeck
2007-11-08 9:07 ` Richard Guenther
2007-11-08 13:48 ` Kenneth Zadeck [this message]
[not found] <4731FAA9.1050100@naturalbridge.com>
2007-11-12 10:17 ` Razya Ladelsky
2007-11-12 13:22 ` Richard Guenther
2007-11-12 15:28 ` Razya Ladelsky
2007-11-12 15:38 ` Richard Guenther
2007-11-12 17:08 ` Mark Mitchell
2007-11-20 13:47 ` Razya Ladelsky
2007-11-20 13:49 ` Manfred Hollstein
2007-11-20 14:51 ` Richard Guenther
2007-11-13 20:11 ` Ian Lance Taylor
2007-11-15 16:42 ` Razya Ladelsky
2007-11-15 19:43 ` Ian Lance Taylor
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=473313A6.2050102@naturalbridge.com \
--to=zadeck@naturalbridge.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=janis187@us.ibm.com \
--cc=jsm@polyomino.org.uk \
--cc=richard.guenther@gmail.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).