From: Ayal Zaks <ZAKS@il.ibm.com>
To: Revital1 Eres <ERES@il.ibm.com>
Cc: abel@ispras.ru, gcc-patches@gcc.gnu.org, volodyan@gmail.com
Subject: Re: [PATCH][Modulo-sched] Avoid SMS when the candidate loop contains INC instruction
Date: Thu, 26 Jul 2007 11:34:00 -0000 [thread overview]
Message-ID: <OF50057B75.B83E6822-ONC2257324.003C3ED4-C2257324.003D0F26@il.ibm.com> (raw)
In-Reply-To: <OF75BAE848.B63E5DE5-ONC2257323.005B1F08-C2257324.003B7333@LocalDomain>
Revital1 Eres/Haifa/IBM wrote on 26/07/2007 13:49:21:
> Hello,
>
> We decided to break Patch 1 of 2 into sub-patches and insert them
> gradually. (http://gcc.gnu.org/ml/gcc-patches/2007-07/msg01515.html)
>
> This is the first one which avoids performing SMS when the candidate
> loop contains auto-increment instruction.
>
> The testcase attached is inspired from array_constructor_12.f90 testcase.
>
> This patch was bootstrapped and tested on ppc64 with -fmodulo-sched
> flag. (all languages except Ada)
>
> :ADDPATCH modulo-sched:
>
> OK for mainline?
>
OK, if passes on another platform as well.
This is similar to the single_set restriction; we should revisit them both.
Ayal.
> Thanks,
> Revital
>
> 2007-07-26 Vladimir Yanovsky <yanov@il.ibm.com>
>
> * modulo-sched.c (sms_schedule): Avoid loops which includes
> auto-increment instructions.
>
> * testsuite/gfortran.dg/sms-1.f90: New test.
>
> [attachment "autoinc_patch.txt" deleted by Ayal Zaks/Haifa/IBM]
[attachment
> "sms-1.f90.txt" deleted by Ayal Zaks/Haifa/IBM]
next parent reply other threads:[~2007-07-26 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF75BAE848.B63E5DE5-ONC2257323.005B1F08-C2257324.003B7333@LocalDomain>
2007-07-26 11:34 ` Ayal Zaks [this message]
2007-07-26 11:06 Revital1 Eres
2007-07-26 16:40 ` Kenneth Zadeck
2007-07-26 18:21 ` Ayal Zaks
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=OF50057B75.B83E6822-ONC2257324.003C3ED4-C2257324.003D0F26@il.ibm.com \
--to=zaks@il.ibm.com \
--cc=ERES@il.ibm.com \
--cc=abel@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=volodyan@gmail.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).