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: New loop unroller broken?

From: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
To: Ulrich Weigand <weigand at i1 dot informatik dot uni-erlangen dot de>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>,gcc mailing list <gcc at gcc dot gnu dot org>
Date: Thu, 22 Jan 2004 21:09:50 +0100
Subject: Re: New loop unroller broken?
References: <20040122194127.GC16240@atrey.karlin.mff.cuni.cz> <200401222006.VAA04380@faui1d.informatik.uni-erlangen.de>

Hello,

> > I would definitely like to do something with this in 3.5; if everything
> > goes as I plan, I should have a new doloop pass that will be possible to
> > run after unrolling ready in about two weeks.
> 
> I'm not sure I understand why the only way to fix this problem is
> to run doloop after unrolling; shouldn't the doloop'ized form of
> the loop also be recognizable as having constant iteration count?

yes; but it would make the code to handle it much uglier.  I will
probably make this somehow work for 3.4, but I don't think it is a good
idea long term.

Zdenek

References:
- Re: New loop unroller broken?
  - From: Zdenek Dvorak
- Re: New loop unroller broken?
  - From: Ulrich Weigand

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