aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorWei Wentao <weiwt.fnst@cn.fujitsu.com>2020-07-22 10:16:34 +0100
committerRichard Sandiford <richard.sandiford@arm.com>2020-07-22 10:16:34 +0100
commite93676fb5385200b249cd1c53d95e1d6f717edaa (patch)
tree73d3ac2464e3bab6075439d175c28488cd1648e8 /gcc
parentc58dde88902856eaeb284f3d521a2742b5958aeb (diff)
downloadgcc-e93676fb5385200b249cd1c53d95e1d6f717edaa.zip
gcc-e93676fb5385200b249cd1c53d95e1d6f717edaa.tar.gz
gcc-e93676fb5385200b249cd1c53d95e1d6f717edaa.tar.bz2
doc: fix a typo in languages.texi
gcc/ * doc/languages.texi: Fix “then”/“than” typo.
Diffstat (limited to 'gcc')
-rw-r--r--gcc/doc/languages.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/doc/languages.texi b/gcc/doc/languages.texi
index 7064148..c6144f2 100644
--- a/gcc/doc/languages.texi
+++ b/gcc/doc/languages.texi
@@ -21,7 +21,7 @@ GCC, has several advantages:
target machines already present in GCC@.
@item GCC front ends benefit from all the optimizations in GCC@. Some
of these, such as alias analysis, may work better when GCC is
-compiling directly from source code then when it is compiling from
+compiling directly from source code than when it is compiling from
generated C code.
@item Better debugging information is generated when compiling
directly from source code than when going via intermediate generated C