summaryrefslogtreecommitdiffstats
path: root/gcc/loop.c
diff options
context:
space:
mode:
authorlaw <law@138bc75d-0d04-0410-961f-82ee72b054a4>1999-03-25 16:31:16 +0000
committerlaw <law@138bc75d-0d04-0410-961f-82ee72b054a4>1999-03-25 16:31:16 +0000
commitf4d26d6b1d6c5a7cf7d48054f079cb7e4c7e92db (patch)
tree7eacfd507f08a29cd534e0fb8eb8d689122115e8 /gcc/loop.c
parentc76d0e72d18112c4c6775b513ce6aab808febe8e (diff)
downloadppe42-gcc-f4d26d6b1d6c5a7cf7d48054f079cb7e4c7e92db.tar.gz
ppe42-gcc-f4d26d6b1d6c5a7cf7d48054f079cb7e4c7e92db.zip
* loop.c (strength_reduce): Correct a comment.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@25983 138bc75d-0d04-0410-961f-82ee72b054a4
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 c218edaa549..7f3b51d03fe 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
OpenPOWER on IntegriCloud