public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Revital Eres <revital.eres@linaro.org>
To: gcc-patches@gcc.gnu.org
Cc: rakdver@kam.mff.cuni.cz, Patch Tracking <patches@linaro.org>,
	zaks@il.ibm.com
Subject: [PATCH, SMS 3/3] Skip DEBUG_INSN in loop-doloo​​p.
Date: Sun, 08 May 2011 09:20:00 -0000	[thread overview]
Message-ID: <BANLkTikEFMz3vFZZ-mUcgx+fPwwA2uBBRQ@mail.gmail.com> (raw)
Message-ID: <20110508092000.gZo8gCncV0qmIxbB1327ng-LjQx-UykpnigbX5Anc9M@z> (raw)

Hello,

(sorry for multiple copies of this email)

This small fix was inserted to skip DEBUG_INSNs while
recognizing doloop pattern in loop-doloop.c file.  It's a fix
for the already approved do-loop patch (not in mainline yet,
http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01718.html) in loop-doloop.c

The patch was tested together with the rest of the patches in this series
and on top of the patch to support do-loop for ARM (not yet in mainline,
but approved http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01718.html).
On ppc64-redhat-linux regtest as well as bootstrap with SMS flags
enabling SMS also on loops with stage count 1.  Regtested on SPU.
On arm-linux-gnueabi regtseted on c,c++. Bootstrap c language with SMS
flags enabling SMS also on loops with stage count 1.

OK for mainline?

Thanks,
Revital

Changelog:

     * loop-doloop.c (doloop_condition_get): Use prev_nondebug_insn
        instead of PREV_INSN.

--- loop-doloop.c       2011-05-07 16:08:27.000000000 +0300
+++ loop-doloop_new.c   2011-05-07 16:07:48.000000000 +0300
@@ -151,7 +151,7 @@ doloop_condition_get (rtx doloop_pat)
          inc = XVECEXP (PATTERN (prev_insn), 0, 1);
        }
       else
-        inc = PATTERN (PREV_INSN (doloop_pat));
+        inc = PATTERN (prev_insn);
       /* We expect the condition to be of the form (reg != 0)  */
       cond = XEXP (SET_SRC (cmp), 0);
       if (GET_CODE (cond) != NE || XEXP (cond, 1) != const0_rtx)

             reply	other threads:[~2011-05-08  7:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08  7:39 Revital Eres [this message]
2011-05-08  7:49 ` Revital Eres
2011-05-08  9:20 ` Revital Eres
2011-05-08 10:57 ` Revital Eres
2011-05-08  7:41 [PATCH, SMS 3/3] Skip DEBUG_INSN in loop-doloo​​​p Revital Eres
2011-05-08  8:48 ` Revital Eres
2011-05-08 11:40 ` Revital Eres
2011-05-08  9:10 [PATCH, SMS 3/3] Skip DEBUG_INSN in loop-doloo​​​​p Revital1 Eres
2011-05-08 12:02 ` Revital1 Eres

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=BANLkTikEFMz3vFZZ-mUcgx+fPwwA2uBBRQ@mail.gmail.com \
    --to=revital.eres@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=patches@linaro.org \
    --cc=rakdver@kam.mff.cuni.cz \
    --cc=zaks@il.ibm.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).