invoke.texi (-ffat-lto-objects): Clarify that gcc-ar et.al.

2012-06-04  Andi Kleen <ak@linux.intel.com>

	* doc/invoke.texi (-ffat-lto-objects): Clarify that gcc-ar
	et.al. should be used.

From-SVN: r191052

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 5aa6aa84a0890408d401b6660ba305a0a9fffbe9..1c910cbaad3d64247e317c2ea352962a5258263c 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2012-06-04  Andi Kleen <ak@linux.intel.com>
+
+       * doc/invoke.texi (-ffat-lto-objects): Clarify that gcc-ar
+       et.al. should be used.
+
 2012-09-06  Andi Kleen  <ak@linux.intel.com>
 
        * gcc/lto-streamer.h (res_pair): Add.

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 6794313ab777d0551020b4f4bac7c8d68936ed0d..3c46cd90a55c6d754df3919b027e1fad7b929d78 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -8138,7 +8138,9 @@ requires the complete toolchain to be aware of LTO. It requires a linker with
 linker plugin support for basic functionality.  Additionally,
 @command{nm}, @command{ar} and @command{ranlib}
 need to support linker plugins to allow a full-featured build environment
-(capable of building static libraries etc).
+(capable of building static libraries etc). gcc provides the @command{gcc-ar},
+@command{gcc-nm}, @command{gcc-ranlib} wrappers to pass the right options
+to these tools. With non fat LTO makefiles need to be modified to use them.
 
 The default is @option{-ffat-lto-objects} but this default is intended to
 change in future releases when linker plugin enabled environments become more