This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[wwwdocs,committed] 4.5/changes.html: Add link to manual for -flto
- From: Tobias Burnus <burnus at net-b dot de>
- To: gcc-patches at gcc dot gnu dot org
- Cc: gerald at pfeifer dot com
- Date: Thu, 15 Oct 2009 15:34:53 +0200
- Subject: [wwwdocs,committed] 4.5/changes.html: Add link to manual for -flto
I have added a hyperlink to http://gcc.gnu.org/gcc-4.5/changes.html 's
-flto entry, linking to -flto in the manual.
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
Especially (b) was (is?) assumed by several people; thus one could
actually think of mentioning -fwhole-program in the release notes.
Tobias
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.5/changes.html,v
retrieving revision 1.39
diff -u -r1.39 changes.html
--- changes.html 10 Oct 2009 21:19:22 -0000 1.39
+++ changes.html 15 Oct 2009 13:25:49 -0000
@@ -48,7 +48,9 @@
supported before; for those a fall back is used if MPC is not
available.</li>
- <li>A new link-time optimizer has been added (<code>-flto</code>).
+ <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
cvs commit: Examining .
Checking in changes.html;
/cvs/gcc/wwwdocs/htdocs/gcc-4.5/changes.html,v <-- changes.html
new revision: 1.40; previous revision: 1.39
done