[DOC,OBVIOUS] Fix typo in LTO documentation (PR lto/50345).

Submitted by Martin Liška on April 19, 2017, noon


Message ID 6d7f12b8-e4e9-d3ad-17d4-d110d8e002c9@suse.cz
State New
Headers show

Commit Message

Martin Liška April 19, 2017, noon
Simple patch that's attached here:

Installed as obvious.


Patch hide | download patch | download mbox

From 175a12777c8c17e9fbd0fb00c78ecb6c9c6b528e Mon Sep 17 00:00:00 2001
From: marxin <mliska@suse.cz>
Date: Wed, 19 Apr 2017 13:56:29 +0200
Subject: [PATCH] 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'.
 gcc/doc/lto.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/doc/lto.texi b/gcc/doc/lto.texi
index 1d36f744d55..990c06f9444 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