This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Development plan *ducks* (Re: Loop optimizer issues)
- From: Jan Hubicka <jh at suse dot cz>
- To: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>
- Cc: Jan Hubicka <jh at suse dot cz>, Zack Weinberg <zack at codesourcery dot com>,Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>,David Edelsohn <dje at watson dot ibm dot com>,Diego Novillo <dnovillo at redhat dot com>,gcc mailing list <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, Daniel Berlin <dberlin at dberlin dot org>
- Date: Tue, 29 Jul 2003 18:57:34 +0200
- Subject: Re: Development plan *ducks* (Re: Loop optimizer issues)
- References: <20030728191927.GA26264@atrey.karlin.mff.cuni.cz> <200307281936.PAA30478@makai.watson.ibm.com> <20030728204001.GA31710@atrey.karlin.mff.cuni.cz> <1059429748.3649.77.camel@steven.lr-s.tudelft.nl> <8765lm7178.fsf@egil.codesourcery.com> <1059434004.3647.156.camel@steven.lr-s.tudelft.nl> <20030728233200.GH27638@kam.mff.cuni.cz> <1059472209.3651.64.camel@steven.lr-s.tudelft.nl>
> For example, bug 11131, a mainline regression, doesn't look related to
> unit-at-a-time. But I just found out that your unit-at-a-time patch
> seems to have caused that bug to re-appear. It's a pessimizes-code bug,
> so regtesting could have missed it. Now in this case there's a test
> case for it, but who knows what else may be wrong that we don't know
> about yet?
Well, this is the case of about any GCC patch.
I remember I fixed template1.C failure once already. I will try to
figure out what happent to the patch. I remmeber that it was related to
some hack in C++ cannot_inline function.
Honza
>
> > We are about to build all the SuSE Linux pakcages with unit-a-t-atime so
> > it should get enought testing in a week or so.
>
> Cool, good luck! Will those packages be available for download? ;-p
>
> Gr.
> Steven
>