public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Revital1 Eres <ERES@il.ibm.com>
To: Ayal Zaks <ZAKS@il.ibm.com>
Cc: abel@ispras.ru, gcc-patches@gcc.gnu.org,
	Kenneth.Zadeck@NaturalBridge.com,         volodyan@gmail.com
Subject: Re: [PING][PATCH] [modulo-sched] Change the ddg's construction
Date: Mon, 30 Jul 2007 20:59:00 -0000	[thread overview]
Message-ID: <OFC3C75E29.E736E842-ONC2257328.0070FBFC-C2257328.00714808@il.ibm.com> (raw)
In-Reply-To: <OF17F488BC.1FC95BA6-ONC2257328.007046C4-C2257328.0070CC91@LocalDomain>



> > I'll address this in a separate patch which means we currently do not
> > exclude uses that appears inside a REG_EQUAL or REG_EQUIV note; I've
> > added ??? mark to revisit this issue later on.
> >
> > Attached is the patch including the comments.
> >
> > OK to mainline?
> >

> OK.
>
> Instead of checking
> > +          if (INSN_UID (first_def->insn) != INSN_UID (last_def->insn))
> for anti-deps you could simply check
> > +      if (last_def->id == first_def->id)
> as done for output-deps.
>
> Ayal.

I'll check it in with this change.

Revital
>
> > Thanks,
> > Revital

> > 2007-07-30  Revital Eres  <eres@il.ibm.com>
> >
> >         * ddg.c (add_deps_for_def): Rename to...
> >         (add_cross_iteration_register_deps): This.  Change
implementation
> >         to use only reaching def and def-use chains to construct the
> >         inter loop dependencies.
> >         (add_deps_for_use): Remove function.
> >         (build_inter_loop_deps): Call add_cross_iteration_register_deps
> >         function to build the inter loop dependencies.
> >         * modulo-sched.c (sms_schedule): Build only
> >         reaching def and def-use chains for the propose of the ddg
> >         construction.
> >
> > [attachment "patch_ddg_30.txt" deleted by Ayal Zaks/Haifa/IBM]

       reply	other threads:[~2007-07-30 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF17F488BC.1FC95BA6-ONC2257328.007046C4-C2257328.0070CC91@LocalDomain>
2007-07-30 20:59 ` Revital1 Eres [this message]
     [not found] <OF3CA27F68.A9D59391-ONC2257328.003BB6AF-C2257328.0069A46E@LocalDomain>
2007-07-30 21:10 ` Ayal Zaks
     [not found] <OFE62D2EF3.8267B02E-ONC2257323.00727FE2-C2257327.0060B593@LocalDomain>
2007-07-29 22:21 ` Ayal Zaks
2007-07-29 22:23   ` Kenneth Zadeck
2007-07-30 19:35   ` Revital1 Eres
2007-07-30 19:55     ` Kenneth Zadeck
2007-07-29 18:55 Revital1 Eres
2007-07-29 19:55 ` Kenneth Zadeck

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=OFC3C75E29.E736E842-ONC2257328.0070FBFC-C2257328.00714808@il.ibm.com \
    --to=eres@il.ibm.com \
    --cc=Kenneth.Zadeck@NaturalBridge.com \
    --cc=ZAKS@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).