From: Dorit Naishlos <DORIT@il.ibm.com>
To: Mostafa Hagog <MUSTAFA@il.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: SMS improvements branch
Date: Sun, 12 Dec 2004 11:35:00 -0000 [thread overview]
Message-ID: <OF9D48FDDF.94D688A0-ONC2256F68.003B0ECF-C2256F68.003FB3E3@il.ibm.com> (raw)
In-Reply-To: <OFF1168A3F.242E16ED-ONC2256F65.0052C0B6-C2256F65.006C8D96@il.ibm.com>
> I am thinking of opening a development branch for the sake of SMS
> improvements, unless someone knows of an existing branch that
> this work could be put in.
I think the autovect-branch could be an option - it is intended to host
work on loop optimizations. Also sounds like some of the infrastructure you
need for SMS is related to infrastructure developed on autovect (inter-loop
dependences for example). Another thing in common to SMS and vectorization
is that both target single-basic-block countable loops. I don't know if SMS
would directly benefit from the tree-level loop-optimization work that
is/will be taking place in autovect-branch, but I'm sure vectorized loops
would benefit from SMS.
dorit
Mostafa
Hagog/Haifa/IBM@I To: gcc@gcc.gnu.org
BMIL cc:
Sent by: Subject: SMS improvements branch
gcc-owner@gcc.gnu
.org
09/12/2004 21:45
There are several improvements of SMS that were introduced to 4.0 but
rejected and are waiting for 4.1 to open. There is also additional
work that we are planning to do for improving SMS, here is a list
of the items and their status:
I. Infrastructure work:
1. Change SMS to work in cfglayout mode. (DONE, for 4.1)
2. Build and use loop information in SMS. (DONE, for 4.1)
3. Add loop versioning to RTL (in cfglayout mode). (DONE, for 4.1)
4. Loop peeling in SMS to make SMS applicable for more loops.
(Started, for 4.1)
5. Use doloop analysis instead of BCT to check for counted loops.
(Started, for 4.1)
6. Port tree data dependency analysis routines to the RTL level
so we can have better dependancy. (Future, Beyond 4.1)
7. Improve alias analysis in the RTL level. (Future, Beyond 4.1)
II. SMS related work :
1. Use of alias sets to remove memory dependencies. (DONE, for 4.1)
2. Remove register anti-dependencies. (DONE, for 4.1)
3. Add backtracking to the SMS. (DONE, for 4.1)
4. Consider register pressure in SMS. (Beyond 4.1)
I am thinking of opening a development branch for the sake of SMS
improvements, unless someone knows of an existing branch that
this work could be put in.
Mostafa.
next prev parent reply other threads:[~2004-12-12 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 20:41 Mostafa Hagog
2004-12-12 11:35 ` Dorit Naishlos [this message]
2004-12-23 15:14 ` Mostafa Hagog
2004-12-23 18:29 ` Devang Patel
2004-12-13 11:03 ` Sebastian Pop
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=OF9D48FDDF.94D688A0-ONC2256F68.003B0ECF-C2256F68.003FB3E3@il.ibm.com \
--to=dorit@il.ibm.com \
--cc=MUSTAFA@il.ibm.com \
--cc=gcc@gcc.gnu.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).