From: Tobias Burnus <burnus@net-b.de>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org, Diego Novillo <dnovillo@google.com>
Subject: Re: [wwwdocs,committed] 4.5/changes.html: Add link to manual for -flto
Date: Mon, 19 Oct 2009 15:13:00 -0000 [thread overview]
Message-ID: <4ADC8156.1080608@net-b.de> (raw)
In-Reply-To: <alpine.LSU.1.99.0910162330320.5525@acrux.dbai.tuwien.ac.at>
On 10/16/2009 11:31 PM, Gerald Pfeifer wrote:
> On Thu, 15 Oct 2009, Tobias Burnus wrote:
>
>> My hope is that this increases the chance that people read the relevant
>> entry in the manual and that they thus realize
>> a) that -flto has to be used at both compile and link time -- and
>> b) that -fwhole-program is not implied by -flto
>>
> Yes, those are two pitfalls we'll encounter regularily. I wonder
> whether in addition to adding the link (which is surely fine), you
> may want to put these two points into the changes.html file as well?
>
How about the following? (I copied the strings from the -flto entry. It
indirectly points to -fwhopr, which is presumably okay: That way the
option is made know, but not too prominently - especially as -fwhopr
does not work properly, yet.)
Tobias
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.5/changes.html,v
retrieving revision 1.42
diff -U10 -r1.42 changes.html
--- changes.html 17 Oct 2009 11:20:34 -0000 1.42
+++ changes.html 19 Oct 2009 15:09:29 -0000
@@ -51,21 +51,29 @@
<li>A new link-time optimizer has been added (<code><a
href="http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-flto-795"
>-flto</a></code>).
When this flag is used, GCC generates a bytecode representation of
each input file and writes it to special ELF sections in each
object file. When the object files are linked together, all the
function bodies are read from these ELF sections and instantiated
as if they had been part of the same translation unit. This
enables interprocedural optimizations to work across different
files (and even different languages), potentially improving the
- performance of the generated code.</li>
+ performance of the generated code. To use the link-timer optimizer,
+ <code>-flto</code> needs to be specified at compile time and during
+ the final link. If the program does not require any symbols to be
+ exported, it is possible to combine -flto and <code><a
+
href="http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-fwhopr-796"
+ >-fwhopr</a></code> with <code><a
+
href="http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-fwhole_002dprogram-794"
+ >-fwhole-program</a></code> to allow the interprocedural optimizers
+ to use more aggressive assumptions.</li>
</ul>
<h2>New Languages and Language specific improvements</h2>
<h3>All languages</h3>
<ul>
<li>The <code>-fshow-column</code> option is now on by default. This
means error messages now have a column associated with them.</li>
</ul>
next prev parent reply other threads:[~2009-10-19 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 13:36 Tobias Burnus
2009-10-16 21:34 ` Gerald Pfeifer
2009-10-19 15:13 ` Tobias Burnus [this message]
2009-10-19 22:37 ` Gerald Pfeifer
2009-10-20 12:07 ` Diego Novillo
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=4ADC8156.1080608@net-b.de \
--to=burnus@net-b.de \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).