From: Andreas Jaeger <aj@suse.de>
To: scox@redhat.com
Cc: ritu@csa.iisc.ernet.in, gcc@gcc.gnu.org
Subject: Re: Loop dependence analysis!!
Date: Wed, 16 Oct 2002 13:16:00 -0000 [thread overview]
Message-ID: <u8elaq2pl4.fsf@gromit.moeb> (raw)
In-Reply-To: <200210161455.g9GEtq701173@scox.rdu.redhat.com> (scox@redhat.com's message of "Wed, 16 Oct 2002 10:55:52 -0400")
scox@redhat.com writes:
>> Or will the rest get added at some point?
>
> The front end didn't have the infrastructure to recognize and analyze
> loops, so it was easier to wait until that was available. Now that it
> is becoming available it will be possible to hook that in and make it
> useful. It pretty much implements the GCD test.
What kind of infrastructure do you speak about? The new loop
optimizer done by Zdenek, etc? In that case it might make sense to
add your code to the rtlopt branch...
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-10-16 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 9:43 scox
2002-10-16 13:16 ` Andreas Jaeger [this message]
2002-10-16 13:23 ` Diego Novillo
2002-10-16 13:53 ` Pop Sébastian
2002-10-16 13:58 ` Diego Novillo
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 2:40 Ritu Sabharwal
2002-10-16 2:55 ` Andreas Jaeger
2002-10-17 14:55 ` Ritu Sabharwal
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=u8elaq2pl4.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=ritu@csa.iisc.ernet.in \
--cc=scox@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).