aboutsummaryrefslogtreecommitdiff
path: root/gcc/loop.c
diff options
context:
space:
mode:
authorFinn Hakansson <finn@axis.com>1999-03-25 16:31:16 +0000
committerJeff Law <law@gcc.gnu.org>1999-03-25 09:31:16 -0700
commitcc29143343f0b7dc59c9d0f8399ac1135e947b0c (patch)
tree7eacfd507f08a29cd534e0fb8eb8d689122115e8 /gcc/loop.c
parentcf38f48a33db6760662fb12716f87b3e3a9ac732 (diff)
downloadgcc-cc29143343f0b7dc59c9d0f8399ac1135e947b0c.zip
gcc-cc29143343f0b7dc59c9d0f8399ac1135e947b0c.tar.gz
gcc-cc29143343f0b7dc59c9d0f8399ac1135e947b0c.tar.bz2
* loop.c (strength_reduce): Correct a comment.
From-SVN: r25983
Diffstat (limited to 'gcc/loop.c')
-rw-r--r--gcc/loop.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/loop.c b/gcc/loop.c
index c218eda..7f3b51d 100644
--- a/gcc/loop.c
+++ b/gcc/loop.c
@@ -4149,10 +4149,10 @@ strength_reduce (scan_start, end, loop_top, insn_count,
this can't succeed if we already know that there is a jump
between v->insn and next->insn, yet next->always_executed is
set and next->maybe_multiple is cleared. Such a combination
- implies that the jump destination is outseide the loop.
+ implies that the jump destination is outside the loop.
If we want to make this check more sophisticated, we should
check each branch between v->insn and next->insn individually
- to see if it the biv is dead at its destination. */
+ to see if the biv is dead at its destination. */
if (uid_luid[REGNO_LAST_UID (bl->regno)] < INSN_LUID (loop_end)
&& bl->init_insn