aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-cfg.c
diff options
context:
space:
mode:
authorKazu Hirata <kazu@cs.umass.edu>2005-05-19 03:05:49 +0000
committerKazu Hirata <kazu@gcc.gnu.org>2005-05-19 03:05:49 +0000
commit128a79fb0142757127a8ded0635ce6f4f94ecbba (patch)
tree2515da9a6676ddb153df106225173fc9b07d620d /gcc/tree-cfg.c
parentf75aac9e435b093bed7dbacf192453c2147e1503 (diff)
downloadgcc-128a79fb0142757127a8ded0635ce6f4f94ecbba.zip
gcc-128a79fb0142757127a8ded0635ce6f4f94ecbba.tar.gz
gcc-128a79fb0142757127a8ded0635ce6f4f94ecbba.tar.bz2
cfgexpand.c, [...]: Fix comment typos.
gcc/ * cfgexpand.c, tree-cfg.c, tree-inline.c, tree-optimize.c, tree-ssa-forwprop.c: Fix comment typos. * doc/invoke.texi: Fix a typo. cp/ * parser.c: Fix comment typos. From-SVN: r99944
Diffstat (limited to 'gcc/tree-cfg.c')
-rw-r--r--gcc/tree-cfg.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/tree-cfg.c b/gcc/tree-cfg.c
index c141982..9eeb783 100644
--- a/gcc/tree-cfg.c
+++ b/gcc/tree-cfg.c
@@ -1359,7 +1359,7 @@ replace_uses_by (tree name, tree val)
x = w * w;
If we performed the update in the first loop, the statement
- would be rescanned after first occurence of w is replaced,
+ would be rescanned after first occurrence of w is replaced,
the new uses would be placed to the beginning of the list,
and we would never process them. */
for (i = 0; VEC_iterate (tree, stmts, i, stmt); i++)
@@ -1398,7 +1398,7 @@ tree_merge_blocks (basic_block a, basic_block b)
{
gcc_assert (is_gimple_reg (def));
- /* Note that just emiting the copies is fine -- there is no problem
+ /* Note that just emitting the copies is fine -- there is no problem
with ordering of phi nodes. This is because A is the single
predecessor of B, therefore results of the phi nodes cannot
appear as arguments of the phi nodes. */