Re: GCC 4.0.1 Status (2005-06-05)

2005-06-13 Thread Geoffrey Keating
Mark Mitchell <[EMAIL PROTECTED]> writes: > Andrew Pinski wrote: > > On Jun 5, 2005, at 1:41 PM, Devang Patel wrote: > > > >> > >> On Jun 5, 2005, at 10:18 AM, Mark Mitchell wrote: > >> > >>> Here are three bugs I'd really like to see fixed. > >>> > >>> * 21528: SRA and/or aliasing problem. > >>>

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Mark Mitchell
Diego Novillo wrote: On Sun, Jun 05, 2005 at 10:18:05AM -0700, Mark Mitchell wrote: * 21528: SRA and/or aliasing problem. I'll take a look at this tomorrow. Thanks! -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Diego Novillo
On Sun, Jun 05, 2005 at 10:18:05AM -0700, Mark Mitchell wrote: > * 21528: SRA and/or aliasing problem. > I'll take a look at this tomorrow. Diego.

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Mark Mitchell
Andrew Pinski wrote: On Jun 5, 2005, at 2:01 PM, Mark Mitchell wrote: I agree that these are both serious, though neither seems to rise to the level of the KDE issues, in that these both affect "only" debugging. PR 19523 affects only stabs, which I do not think is the default on any primary

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Andrew Pinski
On Jun 5, 2005, at 2:01 PM, Mark Mitchell wrote: I agree that these are both serious, though neither seems to rise to the level of the KDE issues, in that these both affect "only" debugging. PR 19523 affects only stabs, which I do not think is the default on any primary or secondary platform

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Mark Mitchell
Andrew Pinski wrote: On Jun 5, 2005, at 1:41 PM, Devang Patel wrote: On Jun 5, 2005, at 10:18 AM, Mark Mitchell wrote: Here are three bugs I'd really like to see fixed. * 21528: SRA and/or aliasing problem. * 21847: DCE over-eagerness. * 20928: IA32 ICE. * 19523: [4.0/4.1 Regression]

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Mark Mitchell
Steven Bosscher wrote: On Sunday 05 June 2005 19:29, Mark Mitchell wrote: Steven Bosscher wrote: On Sunday 05 June 2005 19:18, Mark Mitchell wrote: The reason that this release is slightly ahead of schedule is because of a relatively frequently-encountered wrong-code regression in C++. Wh

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Andrew Pinski
On Jun 5, 2005, at 1:41 PM, Devang Patel wrote: On Jun 5, 2005, at 10:18 AM, Mark Mitchell wrote: Here are three bugs I'd really like to see fixed. * 21528: SRA and/or aliasing problem. * 21847: DCE over-eagerness. * 20928: IA32 ICE. * 19523: [4.0/4.1 Regression] DBX_USE_BINCL support b

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Devang Patel
On Jun 5, 2005, at 10:18 AM, Mark Mitchell wrote: Here are three bugs I'd really like to see fixed. * 21528: SRA and/or aliasing problem. * 21847: DCE over-eagerness. * 20928: IA32 ICE. * 19523: [4.0/4.1 Regression] DBX_USE_BINCL support broken in the C++ compiler 19523 is a nasty regr

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Steven Bosscher
On Sunday 05 June 2005 19:29, Mark Mitchell wrote: > Steven Bosscher wrote: > > On Sunday 05 June 2005 19:18, Mark Mitchell wrote: > >>The reason that this release is slightly ahead of schedule is because of > >>a relatively frequently-encountered wrong-code regression in C++. > > > > Which regress

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Mark Mitchell
Steven Bosscher wrote: On Sunday 05 June 2005 19:18, Mark Mitchell wrote: The reason that this release is slightly ahead of schedule is because of a relatively frequently-encountered wrong-code regression in C++. Which regression is this? The bug that caused KDE miscompilations. > And w

Re: GCC 4.0.1 Status (2005-06-05)

2005-06-05 Thread Steven Bosscher
On Sunday 05 June 2005 19:18, Mark Mitchell wrote: > The reason that this release is slightly ahead of schedule is because of > a relatively frequently-encountered wrong-code regression in C++. Which regression is this? And why does this regression motivate you to suddenly go release 4.0.1 where