From: Andrew Pinski <pinskia@physics.uc.edu>
To: jgrant@reflectionsinteractive.com
Cc: gcc@gcc.gnu.org, ian@wasabisystems.com,
Andrew Pinski <pinskia@physics.uc.edu>
Subject: Re: Optimisation options turned on at a certain level
Date: Sun, 18 Jan 2004 19:29:00 -0000 [thread overview]
Message-ID: <86838479-49EC-11D8-9D69-000393A6D2F2@physics.uc.edu> (raw)
In-Reply-To: <A91F89184D69D411A4E40008C784F4970259F963@MR-T>
On Jan 18, 2004, at 10:28, jgrant@reflectionsinteractive.com wrote:
> Hi Ian
>
> Thanks for the info.
>
>>> Could this be added the documentation? so its clear exactly what is
>>> being done by which options are being passed.
>>
>> My two comments are:
>>
>> 1) Documentation patches are always welcome.
>
> I noticed the info gcc pages were in some ways more detailed, for
> instance
> this optimisation page:
> http://www-es.fernuni-hagen.de/cgi-bin/info2html?
> (gcc)Optimize%20Options
>
> Are the gcc online manual documents maintained by different people
> from the
> gcc info pages? Perhaps some aspects could be combined.
No, the online docs comes from the info pages.
What you are seeing is a newer version of the info pages.
The latest and greatest version of the info page on a web page is
located here:
http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2004-01-18 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 18:26 jgrant
2004-01-18 19:08 ` Ian Lance Taylor
2004-01-18 19:29 ` Andrew Pinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 19:31 jgrant
2003-12-22 11:00 jgrant
2003-12-22 19:31 ` Ian Lance Taylor
2003-12-21 18:30 jgrant
2003-12-21 18:36 ` 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=86838479-49EC-11D8-9D69-000393A6D2F2@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=ian@wasabisystems.com \
--cc=jgrant@reflectionsinteractive.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).