Re: GCC 4.1.2 Status Report

["Daniel Berlin" <dberlin at dberlin dot org>]

On 2/4/07, Mark Mitchell <mark@codesourcery.com> wrote:
> [Danny, Richard G., please see below.]
>
> Thanks to all who have helped tested GCC 4.1.2 RC1 over the last week.
>
> I've reviewed the list traffic and Bugzilla.  Sadly, there are a fair
> number of bugs.  Fortunately, most seem not to be new in 4.1.2, and
> therefore I don't consider them showstoppers.
>
> The following issues seem to be the 4.1.1 regressions:
>
>   http://gcc.gnu.org/wiki/GCC_4.1.2_Status
>
> PR 28743 is only an ICE-on-invalid, so I'm not terribly concerned.
>
> Daniel, 30088 is another aliasing problem.  IIIRC, you've in the past
> said that these were (a) hard to fix, and (b) uncommon.  Is this the
> same problem?  If so, do you still feel that (b) is true?  I'm
> suspicious, and I am afraid that we need to look for a conservative hack.

It's certainly true that people will discover more and more aliasing
bugs the harder they work 4.1 :)
There is always the possibility of turning off the pruning, which will
drop our performance, but will hide most of the latent bugs we later
fixed through rewrites well enough that they can't be triggered (the
4.1 optimizers aren't aggressive enough).