[MAJOR BUG] g++ 2.95.x generates invalid code for KDE 3.3.0

[Ingo Klöcker]

On Sunday 19 September 2004 22:20, Leo Savernik wrote:
> Am Sonntag, 19. September 2004 21:56 schrieb Ingo Klöcker:
> [...]
>
> > > I'm willing to stay the gcc-2.95 compliance police as long as I'm
> > > using gcc-2.95 (as I've already done for the 3.2 and 3.3
> > > releases). I just have to do more thorough testing of the
> > > betas/rcs.
> >
> > I don't think it's sufficient to have one developer check whether
> > KDE still works with gcc-2.95. Actually, the current situation has
> > already proven this point. KDE 3.3.0 doesn't work with gcc-2.95.
> > That's a fact.
>
> In fact it does work, that's what I'm using right now.

That's a matter of definition. I define "KDE 3.3.0 does work" as "All 
apps that are included in KDE 3.3.0 work".

> Only the apps using K*Socket* crash (but those aren't too many,
> apparently). 

See Thiago's reply.

> > We, the KDE PIM developers, have decided to drop KDE 3.2
> > compatibility (KDE PIM is now developed against KDE 3.3) because
> > nobody of us wanted to stay with KDE 3.2 now that KDE 3.3 is out.
> > Nobody of us using KDE 3.2 would have made it impossible to
> > guarantee that KDE PIM still works (or even compiles) with KDE 3.2.
> > So dropping KDE 3.2 compatibility was the sensible conclusion.
>
> Ok, but I'm not nobody. I actively use gcc-2.95 and *will* notice
> bugs (but sometimes too late).

My point is that one person might not be enough.

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040919/2fdaf332/attachment.sig>