This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] doc/*.texi: Fix typos.
- From: Kazu Hirata <kazu at cs dot umass dot edu>
- To: gcc-patches at gcc dot gnu dot org
- Date: Fri, 10 Sep 2004 18:16:55 -0400 (EDT)
- Subject: [patch] doc/*.texi: Fix typos.
Hi,
Committed as obvious.
Kazu Hirata
2004-09-10 Kazu Hirata <kazu@cs.umass.edu>
* doc/tm.texi, doc/tree-ssa.texi: Fix typos.
Index: doc/tm.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/tm.texi,v
retrieving revision 1.367
diff -u -r1.367 tm.texi
--- doc/tm.texi 9 Sep 2004 17:11:18 -0000 1.367
+++ doc/tm.texi 10 Sep 2004 22:11:22 -0000
@@ -9387,7 +9387,7 @@
This target hook returns @code{true} if it is safe to use a local alias
for a virtual function @var{fndecl} when constructing thunks,
@code{false} otherwise. By default, the hook returns @code{true} for all
-functions, if a target supports aliases (ie. defines
+functions, if a target supports aliases (i.e. defines
@code{ASM_OUTPUT_DEF}), @code{false} otherwise,
@end deftypefn
Index: doc/tree-ssa.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/tree-ssa.texi,v
retrieving revision 1.7
diff -u -r1.7 tree-ssa.texi
--- doc/tree-ssa.texi 4 Sep 2004 03:26:58 -0000 1.7
+++ doc/tree-ssa.texi 10 Sep 2004 22:11:23 -0000
@@ -709,7 +709,7 @@
a statement whether a variable of these types has a killing definition.
If the variable does, then the statement is marked as having a
@dfn{must definition} of that variable. However, if a statement is only
-defining a part of the variable (ie. a field in a structure), or if we
+defining a part of the variable (i.e. a field in a structure), or if we
know that a statement might define the variable but we cannot say for sure,
then we mark that statement as having a @dfn{may definition}. For
instance, given