public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Bingfeng Mei <bmei@broadcom.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	"zaks@il.ibm.com" <zaks@il.ibm.com>,
	 	Adrian Ashley <aashley@broadcom.com>
Subject: Re: Solve transitive closure issue in modulo scheduling
Date: Sat, 07 Feb 2009 17:20:00 -0000	[thread overview]
Message-ID: <4aca3dc20902070920u43f5f5bdie812f82c126fe269@mail.gmail.com> (raw)
In-Reply-To: <7FB04A5C213E9943A72EE127DB74F0AD49E39C3E85@SJEXCHCCR02.corp.ad.broadcom.com>

On Fri, Jan 30, 2009 at 7:44 AM, Bingfeng Mei <bmei@broadcom.com> wrote:
> Hello,
> I try to make modulo scheduling work more efficiently for our VLIW target. I found one serious issue that prevents current SMS algorithm from achieving high IPC is so-called "transitive closure" problem, where scheduling window is only calculated using direct predecessors and successors. Because SMS is not an iterative algorithm, this may cause failures in finding a valid schedule. Without splitting rows, some simple loops just cannot be scheduled not matter how big the II is. With splitting rows, schedule can be found, but only at bigger II. GCC wiki (http://gcc.gnu.org/wiki/SwingModuloScheduling) lists this as a TODO. Is there any work going on about this issue (the last wiki update was one year ago)? If no one is working on it, I plan to do it. My idea is to use the MinDist algorithm described in B. Rau's classic paper "iterative modulo scheduling" (http://www.hpl.hp.com/techreports/94/HPL-94-115.html). The same algorithm can also be used to compute better RecMII. The biggest concern is complexity of computing MinDist matrix, which is O(N^3). N is number of nodes in the loop. I remember somewhere GCC coding guide says "never write quadratic algorithm" :-) Is this an absolute requirement?

It's not an absolute requirement, just a general guideline.

We have plenty of quadratic and worse algorithms, and we'd rather see
less of them :)
Obviously, when it comes to things requiring transitive closure, you
can't really do better.

      parent reply	other threads:[~2009-02-07 17:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 16:17 Bingfeng Mei
2009-02-01 23:18 ` Ayal Zaks
2009-02-05 10:45   ` Bingfeng Mei
2009-02-17 12:03     ` Ayal Zaks
2009-03-13  6:43       ` [PATCH] SMS - Pass the actual schedulable rows to compute_split_row Revital1 Eres
2009-06-22 14:10       ` Unnecessary regmoves in modulo scheduler? Bingfeng Mei
2009-06-23 13:41         ` Revital1 Eres
2009-06-23 13:48           ` Bingfeng Mei
2009-06-23 13:56             ` Revital1 Eres
2009-02-07 17:20 ` Daniel Berlin [this message]

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=4aca3dc20902070920u43f5f5bdie812f82c126fe269@mail.gmail.com \
    --to=dberlin@dberlin.org \
    --cc=aashley@broadcom.com \
    --cc=bmei@broadcom.com \
    --cc=gcc@gcc.gnu.org \
    --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).