From: Martin Liska Date: Mon, 29 May 2017 09:12:50 +0000 (+0200) Subject: Backport r246995 X-Git-Tag: releases/gcc-5.5.0~321 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d32fc73eb9b6ba63596228b7f294c1a7b3f985a7;p=thirdparty%2Fgcc.git Backport r246995 2017-05-29 Martin Liska Backport from mainline 2017-04-19 Paulo J. Matos PR lto/50345 * doc/lto.texi: Remove an extra 'that'. From-SVN: r248567 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 8f417fcb6e8e..cb6fa301637e 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,11 @@ +2017-05-29 Martin Liska + + Backport from mainline + 2017-04-19 Paulo J. Matos + + PR lto/50345 + * doc/lto.texi: Remove an extra 'that'. + 2017-05-29 Martin Liska Backport from mainline diff --git a/gcc/doc/lto.texi b/gcc/doc/lto.texi index 41fd97223ac9..25d9cc15ee00 100644 --- a/gcc/doc/lto.texi +++ b/gcc/doc/lto.texi @@ -43,7 +43,7 @@ existing build systems, as one can, for instance, produce archives of the files. Additionally, one might be able to ship one set of fat objects which could be used both for development and the production of optimized builds. A, perhaps surprising, side effect of this feature -is that any mistake in the toolchain that leads to LTO information not +is that any mistake in the toolchain leads to LTO information not being used (e.g.@: an older @code{libtool} calling @code{ld} directly). This is both an advantage, as the system is more robust, and a disadvantage, as the user is not informed that the optimization has