From: Dorit Naishlos <DORIT@il.ibm.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gcc@gcc.gnu.org,
Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>,
Sebastian Pop <sebastian.pop@cri.ensmp.fr>
Subject: Re: [autovect][PATCH]: Re: Simple loops not interchanged?
Date: Sun, 12 Dec 2004 15:16:00 -0000 [thread overview]
Message-ID: <OFE283CC5B.49A6425D-ONC2256F68.0053D3D5-C2256F68.0053ED31@il.ibm.com> (raw)
> i'd like to
> apply this to the autovect branch (Feel free to use
> evolution_function_is_invariant_p in the tests in the vectorizer. It
> should let you catch some more loops than the simple constant test, if
> you can transform them properly)
sure. thanks,
dorit
Daniel Berlin
<dberlin@dberlin. To: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>, Sebastian Pop
org> <sebastian.pop@cri.ensmp.fr>, Dorit Naishlos/Haifa/IBM@IBMIL
Sent by: cc: gcc@gcc.gnu.org
gcc-owner@gcc.gnu Subject: [autovect][PATCH]: Re: Simple loops not interchanged?
.org
12/12/2004 05:58
I've attached a patch that lets us interchange this.
It does two things:
1. It lets the chrec code consider variables invariant in the loop that
matches the chrec variable (loop number) as constant for purposes for the
chrec.
2. It informs the data dependence tester that chrecs that are equal
(ie the same chrec) overlap on every iteration.
This is enough to get this loop to interchange.
Sebastian, unless you have a problem with this, then Dorit, i'd like to
apply this to the autovect branch (Feel free to use
evolution_function_is_invariant_p in the tests in the vectorizer. It
should let you catch some more loops than the simple constant test, if
you can transform them properly)
It includes Richard's testcase in order to make sure we don't regress here
later on.
:)
#### dataref.diff has been removed from this note on December 12, 2004 by
Dorit Naishlos
next reply other threads:[~2004-12-12 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-12 15:16 Dorit Naishlos [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-10 15:36 Richard Guenther
2004-12-10 16:34 ` Daniel Berlin
2004-12-12 3:58 ` [autovect][PATCH]: " Daniel Berlin
2004-12-12 17:59 ` Devang Patel
2004-12-12 18:02 ` Daniel Berlin
2004-12-13 9:46 ` 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=OFE283CC5B.49A6425D-ONC2256F68.0053D3D5-C2256F68.0053ED31@il.ibm.com \
--to=dorit@il.ibm.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=rguenth@tat.physik.uni-tuebingen.de \
--cc=sebastian.pop@cri.ensmp.fr \
/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).