From: Ayal Zaks <ZAKS@il.ibm.com>
To: Revital Eres <revital.eres@linaro.org>
Cc: gcc-patches@gcc.gnu.org, Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH, SMS] Fix violation of memory dependence
Date: Wed, 15 Jun 2011 23:07:00 -0000 [thread overview]
Message-ID: <OF38CC809C.88AFA71A-ONC22578B0.007A5AC6-C22578B0.007A8CEC@il.ibm.com> (raw)
In-Reply-To: <BANLkTikALCMovevvKKXj2VDPw_z1U4hjEA@mail.gmail.com>
> OK for mainline once regtest on arm-linux-gnueabi completes?
ok.
+ else
+ {
+ if (mem_read_insn_p (to->insn))
+ return;
+ else
better do
else if (!mem_read_insn_p (to->insn))
+ create_ddg_dep_no_link (g, from, to, ANTI_DEP, MEM_DEP, 0);
+ }
Ayal.
Revital Eres <revital.eres@linaro.org> wrote on 15/06/2011 11:45:15 AM:
> From: Revital Eres <revital.eres@linaro.org>
> To: Ayal Zaks/Haifa/IBM@IBMIL
> Cc: gcc-patches@gcc.gnu.org, Patch Tracking <patches@linaro.org>
> Date: 15/06/2011 11:45 AM
> Subject: Re: [PATCH, SMS] Fix violation of memory dependence
>
> Hello,
>
> >>> * ddg.c (add_intra_loop_mem_dep): New function.
> >
> > You could check first thing if (from->cuid == to->cuid), for code
clarity.
>
> Attached is the new version of the patch which addresses this.
>
> The patch was re-tested as follows:
> 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 bootstrap c language with SMS
> flags enabling SMS also on loops with stage count 1
> and currently regression testing on c,c++.
>
> OK for mainline once regtest on arm-linux-gnueabi completes?
>
> Thanks,
> Revital
>
> gcc/
> * ddg.c (add_intra_loop_mem_dep): New function.
> (build_intra_loop_deps): Call it.
>
> testsuite/
> * gcc.dg/sms-9.c: New file.
> [attachment "patch_sms_14_6.txt" deleted by Ayal Zaks/Haifa/IBM]
next prev parent reply other threads:[~2011-06-15 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 9:13 Revital Eres
2011-06-14 8:31 ` Ayal Zaks
2011-06-14 8:44 ` Revital Eres
2011-06-14 9:21 ` Revital Eres
2011-06-16 6:27 ` Revital Eres
2011-06-15 23:07 ` Ayal Zaks [this message]
2011-06-16 5:41 ` Revital 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=OF38CC809C.88AFA71A-ONC22578B0.007A5AC6-C22578B0.007A8CEC@il.ibm.com \
--to=zaks@il.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=patches@linaro.org \
--cc=revital.eres@linaro.org \
/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).