On Tue, Sep 4, 2012 at 6:42 PM, Andi Kleen <a...@firstfloor.org> wrote:
> From: Andi Kleen <a...@linux.intel.com>
>
> Make it clear in the documentation that with -fno-fat-lto-objects the
> gcc-* wrappers should be used to pass the linker plugin.
Ok.
Thanks,
Richard.
> gcc/:
>
> 2012-09-04 Andi Kleen <a...@linux.intel.com>
>
> * doc/invoke.texi (-ffat-lto-objects): Clarify that gcc-ar
> et.al. should be used.
> ---
> gcc/doc/invoke.texi | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> index 6cf7cec..197803d 100644
> --- 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
> --
> 1.7.7
>
