diff options
| author | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2006-12-02 02:26:04 +0000 |
|---|---|---|
| committer | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2006-12-02 02:26:04 +0000 |
| commit | fa7637bd157d64d2520105c9dfb3932c13f067e8 (patch) | |
| tree | dd382bd43e9be4352a80ae68890c6ba09ba0cad1 /gcc/tree-ssa-loop-niter.c | |
| parent | b5fb9cbebaa2fb3ee838461dea22677c8cab871e (diff) | |
| download | gcc-fa7637bd157d64d2520105c9dfb3932c13f067e8.tar.gz | |
* builtins.c, cfgloop.h, cgraph.h, config/arm/arm.c,
config/i386/i386.c, config/i386/i386.h, config/mips/mips.h,
config/rs6000/cell.md, config/rs6000/rs6000.c, config/sh/sh.c,
config/sh/sh4-300.md, config/spu/spu-builtins.def,
config/spu/spu-c.c, config/spu/spu-modes.def,
config/spu/spu.c, config/spu/spu.md,
config/spu/spu_internals.h, config/spu/vmx2spu.h,
fold-const.c, fwprop.c, predict.c, tree-data-ref.h,
tree-flow.h, tree-ssa-loop-manip.c, tree-ssa-loop-niter.c,
tree-ssa-pre.c, tree-vect-analyze.c, tree-vect-transform.c,
tree-vectorizer.c, tree-vrp.c: Fix comment typos. Follow
spelling conventions.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@119442 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 34ce6506f34..862f993f3b6 100644 --- a/gcc/tree-ssa-loop-niter.c +++ b/gcc/tree-ssa-loop-niter.c @@ -1831,7 +1831,7 @@ idx_infer_loop_bounds (tree base, tree *idx, void *dta) unsigned char). To make things simpler, we require both bounds to fit into type, although - there are cases where this would not be strightly necessary. */ + there are cases where this would not be strictly necessary. */ if (!int_fits_type_p (high, type) || !int_fits_type_p (low, type)) return true; @@ -2086,7 +2086,7 @@ n_of_executions_at_most (tree stmt, -- if NITER_BOUND->is_exit is true, then everything before NITER_BOUND->stmt is executed at most NITER_BOUND->bound + 1 - times, and everyting after it at most NITER_BOUND->bound times. + times, and everything after it at most NITER_BOUND->bound times. -- If NITER_BOUND->is_exit is false, then if we can prove that when STMT is executed, then NITER_BOUND->stmt is executed as well in the same |