From 431ae0bf8f3ca0fe8820f5c0b1c8970f2c7651f5 Mon Sep 17 00:00:00 2001 From: Kazu Hirata Date: Sat, 11 Sep 2004 08:34:26 +0000 Subject: cfg.texi, [...]: Insert @: after i.e. * doc/cfg.texi, doc/hostconfig.texi, doc/install.texi, doc/invoke.texi, doc/md.texi, doc/tm.texi, doc/tree-ssa.texi: Insert @: after i.e. or e.g. From-SVN: r87346 --- gcc/doc/tree-ssa.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gcc/doc/tree-ssa.texi') diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi index c62dcce..6d03f50 100644 --- a/gcc/doc/tree-ssa.texi +++ b/gcc/doc/tree-ssa.texi @@ -190,7 +190,7 @@ temporary. In general, expressions in GIMPLE consist of an operation and the appropriate number of simple operands; these operands must either be a -GIMPLE rvalue (@code{is_gimple_val}), i.e. a constant or a register +GIMPLE rvalue (@code{is_gimple_val}), i.e.@: a constant or a register variable. More complex operands are factored out into temporaries, so that @smallexample @@ -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 (i.e. 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 -- cgit v1.1