From: Corey Minyard <minyard@acm.org>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Loop optimization bug with Ada front end on PPC (and probably Alpha)
Date: Sat, 17 Nov 2001 01:33:00 -0000 [thread overview]
Message-ID: <3C0274ED.7000708@acm.org> (raw)
In-Reply-To: <20011125175500.A11474@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
Not all loops have loop->top set in this situation, because that's only
set in bottom entry loops, it seems.
I've made some small changes. Here's just the ones to unroll.c (I
didn't include the move of the macro from loop.c into loop.h).
I'm also thinking that it would be good enough to let the loop run to
loop->cont, and not use loop->top at all. It's bootstrapping right now,
so we'll see if this works. I tried on a small testcase, and it seemed
to work.
-Corey
[-- Attachment #2: v1 --]
[-- Type: text/plain, Size: 2046 bytes --]
Index: unroll.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/unroll.c,v
retrieving revision 1.146
diff -u -r1.146 unroll.c
--- unroll.c 2001/11/16 17:08:12 1.146
+++ unroll.c 2001/11/26 16:44:55
@@ -3479,6 +3479,8 @@
int unsigned_p, compare_dir, final_larger;
rtx last_loop_insn;
rtx reg_term;
+ rtx insn;
+ rtx end_loop_scan;
struct iv_class *bl;
loop_info->n_iterations = 0;
@@ -3704,6 +3706,62 @@
if (initial_value == 0)
return 0;
+
+ /* Some code transformations can result in code akin to
+
+ LOOP_BEG
+ goto start;
+ top:
+ i++;
+ start:
+ ...
+ LOOP_CONT
+ if (i < n) goto top;
+ LOOP_END
+
+ In this situation, we skip the increment the first time through
+ the loop, which results in an incorrect estimate of the number
+ of iterations. As we did for GIVs above, adjust the initial value
+ to compensate. */
+
+ off_by_one = 0;
+ if (loop->top)
+ end_loop_scan = loop->top;
+ else
+ end_loop_scan = loop->cont;
+
+ for (insn = loop->start; insn != end_loop_scan; insn = NEXT_INSN (insn))
+ if (GET_CODE (insn) == JUMP_INSN)
+ {
+ if (any_uncondjump_p (insn)
+ && JUMP_LABEL (insn)
+ && INSN_IN_RANGE_P (JUMP_LABEL (insn), insn, loop->end))
+ {
+ if (reg_set_between_p (bl->biv->src_reg, insn, JUMP_LABEL (insn)))
+ off_by_one = 1;
+ break;
+ }
+ /* No idea what's going on. */
+ if (loop_dump_stream)
+ fprintf (loop_dump_stream,
+ "Loop iterations: Confused by jump before loop top.\n");
+ return 0;
+ }
+
+ if (off_by_one)
+ {
+ if (loop_dump_stream)
+ fprintf (loop_dump_stream,
+ "Loop iterations: Basic induction var skips initial incr.\n");
+ if (GET_CODE (increment) != CONST_INT)
+ {
+ if (loop_dump_stream)
+ fprintf (loop_dump_stream,
+ "Loop iterations: Can't adjust with non-constant incr.\n");
+ return 0;
+ }
+ initial_value = plus_constant (initial_value, -INTVAL (increment));
+ }
unsigned_p = 0;
off_by_one = 0;
WARNING: multiple messages have this Message-ID
From: Corey Minyard <minyard@acm.org>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Loop optimization bug with Ada front end on PPC (and probably Alpha)
Date: Mon, 26 Nov 2001 08:58:00 -0000 [thread overview]
Message-ID: <3C0274ED.7000708@acm.org> (raw)
Message-ID: <20011126085800.FjvPTd43XsJFKp3u5g9Blt52ZSTZd5XTgURTcslDu0I@z> (raw)
In-Reply-To: <20011125175500.A11474@redhat.com>
Not all loops have loop->top set in this situation, because that's only
set in bottom entry loops, it seems.
I've made some small changes. Here's just the ones to unroll.c (I
didn't include the move of the macro from loop.c into loop.h).
I'm also thinking that it would be good enough to let the loop run to
loop->cont, and not use loop->top at all. It's bootstrapping right now,
so we'll see if this works. I tried on a small testcase, and it seemed
to work.
-Corey
next prev parent reply other threads:[~2001-11-26 16:58 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 5:20 Corey Minyard
2001-11-13 6:05 ` David Edelsohn
2001-11-14 8:05 ` Corey Minyard
2001-11-13 8:02 ` guerby
2001-11-13 9:48 ` Corey Minyard
2001-11-16 22:19 ` David Edelsohn
2001-11-26 7:39 ` David Edelsohn
2001-11-15 0:48 ` Richard Henderson
2001-11-15 14:19 ` Andreas Schwab
2001-11-15 16:20 ` Richard Henderson
2001-11-25 12:23 ` Richard Henderson
2001-11-18 9:18 ` Richard Henderson
2001-11-27 0:02 ` Richard Henderson
2001-11-25 8:57 ` Andreas Schwab
2001-11-15 18:02 ` Corey Minyard
2001-11-15 19:37 ` Richard Henderson
2001-11-25 15:52 ` Richard Henderson
2001-11-16 3:13 ` Richard Henderson
2001-11-16 3:42 ` Corey Minyard
2001-11-16 8:54 ` Bryce McKinlay
2001-11-26 0:47 ` Bryce McKinlay
2001-11-25 20:27 ` Corey Minyard
2001-11-17 1:33 ` Corey Minyard [this message]
2001-11-17 6:09 ` Corey Minyard
2001-11-26 10:22 ` Corey Minyard
2001-11-17 11:51 ` Richard Henderson
2001-11-17 15:20 ` Corey Minyard
2001-11-26 14:45 ` Corey Minyard
2001-11-18 5:15 ` Corey Minyard
2001-11-18 8:59 ` Richard Henderson
2001-11-19 2:58 ` Corey Minyard
2001-11-19 3:11 ` Richard Henderson
2001-11-19 5:36 ` Corey Minyard
2001-11-19 7:48 ` Richard Henderson
2001-11-19 7:58 ` Corey Minyard
2001-11-19 9:43 ` Richard Henderson
2001-11-19 12:44 ` Corey Minyard
2001-11-19 13:53 ` Richard Henderson
2001-11-20 11:20 ` Corey Minyard
2001-11-27 19:57 ` Corey Minyard
2001-11-27 15:31 ` Richard Henderson
2001-11-27 15:04 ` Corey Minyard
2001-11-27 14:27 ` Richard Henderson
2001-11-27 13:25 ` Corey Minyard
2001-11-27 12:58 ` Richard Henderson
2001-11-27 11:51 ` Corey Minyard
2001-11-27 10:29 ` Richard Henderson
2001-11-27 10:08 ` Corey Minyard
2001-11-26 23:18 ` Richard Henderson
2001-11-26 17:15 ` Corey Minyard
2001-11-26 13:49 ` Richard Henderson
2001-11-26 8:58 ` Corey Minyard
2001-11-25 17:58 ` Richard Henderson
2001-11-25 15:06 ` Corey Minyard
2001-11-15 18:47 Richard Kenner
2001-11-25 15:13 ` Richard Kenner
2001-11-15 19:05 dewar
2001-11-25 15:20 ` dewar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C0274ED.7000708@acm.org \
--to=minyard@acm.org \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).