diff mbox

LTO / invoke.texi: Add some words about static libraries and LTO

Message ID 532D9FD3.8030605@net-b.de
State New
Headers show

Commit Message

Tobias Burnus March 22, 2014, 2:36 p.m. UTC 
Mention gcc-ar, gcc-ranlib, gcc-nm in the documentation.

OK?

Tobias

Comments

Richard Biener March 24, 2014, 9:22 a.m. UTC | #1 
On Sat, Mar 22, 2014 at 3:36 PM, Tobias Burnus <burnus@net-b.de> wrote:
> Mention gcc-ar, gcc-ranlib, gcc-nm in the documentation.
>
> OK?

Ok.

Thanks,
Richard.

> Tobias
>
Gerald Pfeifer April 15, 2014, 3:40 a.m. UTC | #2 
On Sat, 22 Mar 2014, Tobias Burnus wrote:
> Mention gcc-ar, gcc-ranlib, gcc-nm in the documentation.
> 
> OK?

This looks okay to me, except for

  In order to make a static library suitable for both LTO optimization 
  and usual linkage, compile its object files with @option{-flto} 
  @code{-ffat-lto-objects}.

where I don't understand why its @option first and @code second.

And lines appear a bit long.

Gerald
diff mbox

Patch

2014-03-22  Tobias Burnus  <burnus@net-b.de>

	* doc/invoke.texi (-flto): Expand section about
	using static libraries with LTO.

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 4c183a3..78ddde0 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -8664,8 +8664,13 @@  regular (non-LTO) compilation.
 
 If object files containing GIMPLE bytecode are stored in a library archive, say
 @file{libfoo.a}, it is possible to extract and use them in an LTO link if you
-are using a linker with plugin support.  To enable this feature, use
-the flag @option{-fuse-linker-plugin} at link time:
+are using a linker with plugin support.  To create static libraries suitable
+for LTO, use @command{gcc-ar} and @command{gcc-ranlib} instead of @command{ar}
+and @code{ranlib}; to show the symbols of object files with GIMPLE bytecode, use
+@command{gcc-nm}.  Those commands require that @command{ar}, @command{ranlib}
+and @command{nm} have been compiled with plugin support.  At link time, use the the
+flag @option{-fuse-linker-plugin} to ensure that the library participates in
+the LTO optimization process:
 
 @smallexample
 gcc -o myprog -O2 -flto -fuse-linker-plugin a.o b.o -lfoo
@@ -8678,7 +8683,9 @@  to make them part of the aggregated GIMPLE image to be optimized.
 If you are not using a linker with plugin support and/or do not
 enable the linker plugin, then the objects inside @file{libfoo.a}
 are extracted and linked as usual, but they do not participate
-in the LTO optimization process.
+in the LTO optimization process.  In order to make a static library suitable
+for both LTO optimization and usual linkage, compile its object files with
+@option{-flto} @code{-ffat-lto-objects}.
 
 Link-time optimizations do not require the presence of the whole program to
 operate.  If the program does not require any symbols to be exported, it is