diff options
| author | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-09-05 15:24:15 +0000 |
|---|---|---|
| committer | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-09-05 15:24:15 +0000 |
| commit | 912757687975fdabbb85e7f10a96a136347aa43a (patch) | |
| tree | db2d4b4b49c75785725db3dc511e5abdabfec0c9 /gcc/tree-ssa-loop-niter.c | |
| parent | 690a81bd5f175cc0e0d0e63f3228703fd3623e10 (diff) | |
| download | gcc-912757687975fdabbb85e7f10a96a136347aa43a.tar.gz | |
* c-common.c, cfgexpand.c, cgraphunit.c, defaults.h,
et-forest.c, expr.c, gimplify.c, global.c, gthr-lynx.h,
hard-reg-set.h, modulo-sched.c, optabs.c, postreload-gcse.c,
tree-data-ref.c, tree-flow.h, tree-if-conv.c, tree-inline.c,
tree-sra.c, tree-ssa-loop-im.c, tree-ssa-loop-ivopts.c,
tree-ssa-loop-niter.c, tree-ssa-operands.c,
tree-ssa-operands.h, tree-ssa-propagate.c,
tree-ssa-propagate.h, tree-ssa-threadupdate.c, value-prof.c,
vec.c, vec.h: Fix comment typos. Follow spelling conventions.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@87104 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/tree-ssa-loop-niter.c')
| -rw-r--r-- | gcc/tree-ssa-loop-niter.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/tree-ssa-loop-niter.c b/gcc/tree-ssa-loop-niter.c index 7135ceee226..dd5fad9adb5 100644 --- a/gcc/tree-ssa-loop-niter.c +++ b/gcc/tree-ssa-loop-niter.c @@ -190,7 +190,7 @@ number_of_iterations_cond (tree type, tree base0, tree step0, /* We want to take care only of <=; this is easy, as in cases the overflow would make the transformation unsafe the loop does not roll. Seemingly it would make more sense to want to take - care of <, as NE is more simmilar to it, but the problem is that here + care of <, as NE is more similar to it, but the problem is that here the transformation would be more difficult due to possibly infinite loops. */ if (zero_p (step0)) @@ -266,7 +266,7 @@ number_of_iterations_cond (tree type, tree base0, tree step0, obviously if the test for overflow during that transformation passed, we cannot overflow here. Most importantly any loop with sharp end condition and step 1 falls into this - cathegory, so handling this case specially is definitely + category, so handling this case specially is definitely worth the troubles. */ may_xform = boolean_true_node; } |