This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Loop optimizer issues
- From: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>,Diego Novillo <dnovillo at redhat dot com>,"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>,pop at gauvain dot u-strasbg dot fr, Jan Hubicka <jh at suse dot cz>,Daniel Berlin <dberlin at dberlin dot org>
- Date: Mon, 28 Jul 2003 14:54:55 +0200
- Subject: Re: Loop optimizer issues
- References: <s.bosscher@student.tudelft.nl> <1059347334.3641.60.camel@steven.lr-s.tudelft.nl> <200307272312.TAA27976@makai.watson.ibm.com>
Hello,
> >>>>> Steven Bosscher writes:
>
> Steven> Also, look at the deficiencies list. Can all those missing pieces be
> Steven> provided in time for 3.4? (Do they make a difference?)
>
> The current "new" loop unroller optimizer already has a number of
> deficiencies on the GCC 3.4 trunk. The question is whether this rewrite
> addresses some of those regressions as good or better than reverting to
> the old unroller on the trunk. In other words, this is new functionality,
> but is it also a regression fix early in Stage 2 of development?
some of the reported deficiences would be fixed. Many new would be
introduced.
Zdenek