> -ffat-lto-objects is automatically active for hosts not supporting the
> linker plugin. Is gcc-ar$(exeext) unconditionally built and found
> on such hosts? Will gcc-ar work without finding a linker plugin
> on such hosts?
Currently it errors out. I suppose that could be turned into a warning
On Sun, Aug 31, 2014 at 4:51 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> Change the bootstrap-lto config file to use slim (non fat) LTO..
> Speeds up the LTO bootstrap by ~18% on a 4 core system.
>
> This requires using gcc-ar/ranlib in post stage 1 builds, so these
> are passed to all sub build
Andi Kleen writes:
> diff --git a/config/bootstrap-lto-slim.mk b/config/bootstrap-lto-slim.mk
> new file mode 100644
> index 000..9e065e1
> --- /dev/null
> +++ b/config/bootstrap-lto-slim.mk
This file was not supposed to be included anymore. I removed it in my
version. Instead the existing bo
