Patchwork Docs: lto.texi: Fix typo

login
register
mail settings
Submitter 陳韋任
Date Sept. 20, 2012, 8:26 a.m.
Message ID <20120920082659.GA129@cs.nctu.edu.tw>
Download mbox | patch
Permalink /patch/185360/
State New
Headers show

Comments

陳韋任 - Sept. 20, 2012, 8:26 a.m.
Fix typo. The first "are" in the statement should be "and".

Signed-off-by: Chen Wei-Ren <chenwj@iis.sinica.edu.tw>
---
 gcc/doc/lto.texi |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Richard Earnshaw - Sept. 20, 2012, 8:49 a.m.
On 20 Sep 2012, at 09:27, "陳韋任 (Wei-Ren Chen)" <chenwj@iis.sinica.edu.tw> wrote:

>  Fix typo. The first "are" in the statement should be "and".
> 

Ok.

R.


> Signed-off-by: Chen Wei-Ren <chenwj@iis.sinica.edu.tw>
> ---
> gcc/doc/lto.texi |    2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/gcc/doc/lto.texi b/gcc/doc/lto.texi
> index 73fd831..68f8759 100644
> --- a/gcc/doc/lto.texi
> +++ b/gcc/doc/lto.texi
> @@ -455,7 +455,7 @@ alone.  The problem is that propagation of inter-procedural
> information does not work well across functions and variables
> that are called or referenced by other compilation units (such as
> from a dynamically linked library).  We say that such functions
> -are variables are @emph{externally visible}.
> +and variables are @emph{externally visible}.
> 
> To make the situation even more difficult, many applications
> organize themselves as a set of shared libraries, and the default
> -- 
> 1.7.3.4
>
陳韋任 - Sept. 20, 2012, 9:05 a.m.
On Thu, Sep 20, 2012 at 09:49:27AM +0100, rearnsha@arm.com wrote:
> On 20 Sep 2012, at 09:27, "陳韋任 (Wei-Ren Chen)" <chenwj@iis.sinica.edu.tw> wrote:
> 
> >  Fix typo. The first "are" in the statement should be "and".
> > 
> 
> Ok.
> 
> R.

  Thanks. Would you like to commit this for me? :)

Regards,
chenwj

Patch

diff --git a/gcc/doc/lto.texi b/gcc/doc/lto.texi
index 73fd831..68f8759 100644
--- a/gcc/doc/lto.texi
+++ b/gcc/doc/lto.texi
@@ -455,7 +455,7 @@  alone.  The problem is that propagation of inter-procedural
 information does not work well across functions and variables
 that are called or referenced by other compilation units (such as
 from a dynamically linked library).  We say that such functions
-are variables are @emph{externally visible}.
+and variables are @emph{externally visible}.
 
 To make the situation even more difficult, many applications
 organize themselves as a set of shared libraries, and the default