Re: [PATCH, bootstrap]: Add bootstrap-lto-noplugin build configuration (PR65537)

[Gerald Pfeifer <gerald@pfeifer.com>]

On Thu, 26 Mar 2015, Uros Bizjak wrote:
> Thanks, I have added following text to the description:
> 
> --cut here--
>  @item @samp{bootstrap-lto-noplugin}
>  This option is similar to @code{bootstrap-lto}, but is intended for
> -hosts that do not support the linker plugin.
> +hosts that do not support the linker plugin. Please note that static
> +libraries are not compiled with link time optimizations without
> +linker plugin.  Since GCC middle-end and back-end are in libbackend.a,
> +it means that only part of the frontend is actually LTO optimized.
> --cut here--

I believe there were a couple of issues (link time should be link-time
when it's an adjective, middle-end and back-end on the other hand lose
the the dash when used as a noun,...) and I rewrote this a bit.

Thoughts on the below?  Sandra?

Gerald

2015-04-06  Gerald Pfeifer  <gerald@pfeifer.com>

	* doc/install.texi (bootstrap-lto-noplugin): Rewrite. 

Index: doc/install.texi
===================================================================
--- doc/install.texi	(revision 221832)
+++ doc/install.texi	(working copy)
@@ -2525,10 +2525,10 @@
 
 @item @samp{bootstrap-lto-noplugin}
 This option is similar to @code{bootstrap-lto}, but is intended for
-hosts that do not support the linker plugin. Please note that static
-libraries are not compiled with link time optimizations without
-linker plugin.  Since GCC middle-end and back-end are in libbackend.a,
-it means that only part of the frontend is actually LTO optimized.
+hosts that do not support the linker plugin.  Without the linker plugin 
+static libraries are not compiled with link-time optimizations.  Since 
+the GCC middle end and back end are in @file{libbackend.a} this means
+that only the frontend is actually LTO optimized.
 
 @item @samp{bootstrap-debug}
 Verifies that the compiler generates the same executable code, whether