Richard Guenther wrote:
> On Wed, 25 Apr 2007, Diego Novillo wrote:
>
>> Richard Guenther wrote on 04/25/07 03:54:
>>
>>> I guess I can only produce a workaround, as I'm not too deeply into
>>> the aliasing stuff. So I'd prefer if Danny or Diego could have a look
>>> (Danny apperantly doesn't hav
On Wed, 25 Apr 2007, Diego Novillo wrote:
> Richard Guenther wrote on 04/25/07 03:54:
>
> > I guess I can only produce a workaround, as I'm not too deeply into
> > the aliasing stuff. So I'd prefer if Danny or Diego could have a look
> > (Danny apperantly doesn't have time to do so, my bets for
Zdenek Dvorak wrote:
> Hello,
>
>> 4. PR 31360: Missed optimization
>>
>> I don't generally mark missed optimization bugs as P1, but not hoisting
>> loads of zero out of a 4-instruction loop is bad. Zdenek has fixed this
>> on mainline. Andrew says that patch has a bug. So, what's the story her
Hello,
> 4. PR 31360: Missed optimization
>
> I don't generally mark missed optimization bugs as P1, but not hoisting
> loads of zero out of a 4-instruction loop is bad. Zdenek has fixed this
> on mainline. Andrew says that patch has a bug. So, what's the story here?
I found the problem, I wi
Richard Guenther wrote on 04/25/07 03:54:
> I guess I can only produce a workaround, as I'm not too deeply into
> the aliasing stuff. So I'd prefer if Danny or Diego could have a look
> (Danny apperantly doesn't have time to do so, my bets for Diego are
> similar), but I'll give the workaround I
On Tue, 24 Apr 2007, Mark Mitchell wrote:
> 3. PR 30567: Wrong code with -O3 due to aliasing problems
>
> Richard G. has analyzed this and proposed a patch. Richard, is this
> ready to go? If not, do you need help?
I guess I can only produce a workaround, as I'm not too deeply into
the aliasin
On 4/24/07, Mark Mitchell <[EMAIL PROTECTED]> wrote:
2. PR 30222: crash on gcc.target/i386/vectorize1.c
This PR is apparently due to only part of a mainline patch being applied
to 4.2. It was so diagnosed in December 2006, but nobody has identified
the missing part of the mainline patch. Andre
[I apologize to those of you receiving duplicate copies of this mail. I
thought so hard about copying people that I forgot to address to the list.]
Table of contents:
1. PRs
2. Schedule
3. Rationale
If you're in the CC: list, there are possible action items for you
below. (Recent feedback was