summaryrefslogtreecommitdiff
path: root/gcc/doc/tree-ssa.texi
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2004-09-10 22:16:40 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2004-09-10 22:16:40 +0000
commit1a664318e9152ebd1ca4e99f53b715c4d3e28c04 (patch)
treeb451265c53f070cb2b1ebd8173b83442e04b495f /gcc/doc/tree-ssa.texi
parented904873cc64506e905b5bc660dd7d5c5e6114a1 (diff)
downloadgcc-1a664318e9152ebd1ca4e99f53b715c4d3e28c04.tar.gz
* doc/tm.texi, doc/tree-ssa.texi: Fix typos.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@87324 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/tree-ssa.texi')
-rw-r--r--gcc/doc/tree-ssa.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi
index 1c88e9f021c..c62dcce48f4 100644
--- a/gcc/doc/tree-ssa.texi
+++ b/gcc/doc/tree-ssa.texi
@@ -709,7 +709,7 @@ definitions. For globals, structures, and arrays, we can determine from
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