From: Ayal Zaks <ZAKS@il.ibm.com>
To: Richard Henderson <rth@redhat.com>
Cc: Mostafa Hagog <MUSTAFA@il.ibm.com>,
gcc@gcc.gnu.org, David Edelsohn <dje@watson.ibm.com>,
Vladimir Makarov <vmakarov@redhat.com>,
canqun@yahoo.com.cn
Subject: Re: DDG - Implementing Swing Modulo Scheduling in GCC (cont.)
Date: Thu, 11 Dec 2003 16:59:00 -0000 [thread overview]
Message-ID: <OF894FFFFD.3908F847-ONC2256DF9.005A7325-C2256DF9.005C5C83@il.ibm.com> (raw)
>> Our solution is to build a new and different representation of the data
>> dependence information.
>
>Did you look at using the existing def-use graph (du.c)?
The existing def-use graph (in df.c that is) deals with explicit defs, uses
and register information which we don't need.
We need to know all dependences that exist between insns (flow, anti,
output,
or other scheduling fences), and their latency. The original Swing (and
most
other) Modulo-Scheduling algorithm does not care if the dependence is
register
or memory, flow/anti or output. We model that because we have some ideas
how
to improve on the original algorithm. The basic dependence information in
the
schedulers LOG_LINKS is suitable, after enhancing it with edge structures
and
loop-carried edges.
Ayal.
next reply other threads:[~2003-12-11 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 16:59 Ayal Zaks [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 20:00 Ayal Zaks
2003-12-12 2:36 Daniel Berlin
2003-12-10 17:03 Mostafa Hagog
2003-12-11 5:12 ` Richard Henderson
2003-12-11 7:43 ` David Edelsohn
2003-12-11 17:02 ` Vladimir Makarov
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=OF894FFFFD.3908F847-ONC2256DF9.005A7325-C2256DF9.005C5C83@il.ibm.com \
--to=zaks@il.ibm.com \
--cc=MUSTAFA@il.ibm.com \
--cc=canqun@yahoo.com.cn \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=vmakarov@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).