aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
authorPaulo Matos <paulo@matos-sorge.com>2017-04-19 12:00:47 +0000
committerMartin Liska <marxin@gcc.gnu.org>2017-04-19 12:00:47 +0000
commit0f605f729e2059b7b2792e52fb9c7a3f4df7cd1c (patch)
tree3c1e254d477b718ac4289cc5a4ce638d81d3fe66 /gcc/doc
parent5249994efa240f6f6609371fddab0e76d63277fa (diff)
downloadgcc-0f605f729e2059b7b2792e52fb9c7a3f4df7cd1c.zip
gcc-0f605f729e2059b7b2792e52fb9c7a3f4df7cd1c.tar.gz
gcc-0f605f729e2059b7b2792e52fb9c7a3f4df7cd1c.tar.bz2
Fix typo in LTO documentation (PR lto/50345).
2017-04-19 Paulo J. Matos <paulo@matos-sorge.com> PR lto/50345 * doc/lto.texi: Remove an extra 'that'. From-SVN: r246995
Diffstat (limited to 'gcc/doc')
-rw-r--r--gcc/doc/lto.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/doc/lto.texi b/gcc/doc/lto.texi
index 1d36f74..990c06f 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