Re: GCC 4.1.2 Status Report

2007-02-05 Thread Mark Mitchell
Richard Guenther wrote: >> > It's certainly true that people will discover more and more aliasing >> > bugs the harder they work 4.1 :) >> >> Do you think that PR 30088 is another instance of the same problem, and >> that therefore turning off the pruning will fix it? > > Disabling pruning will a

Re: GCC 4.1.2 Status Report

2007-02-05 Thread Richard Guenther
On 2/5/07, Mark Mitchell <[EMAIL PROTECTED]> wrote: Daniel Berlin wrote: >> 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 >> suspiciou

Re: GCC 4.1.2 Status Report

2007-02-05 Thread Mark Mitchell
Daniel Berlin wrote: >> 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 conserva

Re: GCC 4.1.2 Status Report

2007-02-05 Thread Daniel Berlin
On 2/4/07, Mark Mitchell <[EMAIL PROTECTED]> 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,

Re: GCC 4.1.2 Status Report

2007-02-05 Thread Richard Guenther
On Sun, 4 Feb 2007, Mark Mitchell 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,