This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Loop optimizer issues

From: Aldy Hernandez <aldyh at redhat dot com>
To: Pop Sébastian <pop at gauvain dot u-strasbg dot fr>
Cc: Diego Novillo <dnovillo at redhat dot com>, Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Richard Henderson <rth at redhat dot com>, Jason Merrill <jason at redhat dot com>, Jan Hubicka <jh at suse dot cz>, Daniel Berlin <dberlin at dberlin dot org>
Date: Mon, 2 Jun 2003 17:18:10 -0400
Subject: Re: Loop optimizer issues

I'm starting to work on an aldy^H^H^Hutovectorization pass. We seem

Cool :-)

to have most of the infrastructure in place except data analysis and
the loop unroller.  I can probably get away without the loop unroller
for now by unrolling the loops myself.

The unroller can be recycled from the one at rtl level.
However I still don't have the number of iterations a loop will run,
and this seems to be dependent on the IV detector.

Yeah, I'm not too worried about that because by the time I have a good infrastructure, Zdenek will be done with the loop unroller at the tree level and I can just use that ;-).

Should I prepare a patch that registers the loop unroller in the cfg hooks?


Wouldn't hurt.
:)

References:
- Re: Loop optimizer issues
  - From: Pop Sébastian

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]