Re: Bug#190399: Bug#246547: amd64 support for glibc 2.3.2.ds1-14
On Thursday 08 July 2004 21:10, Ron Johnson wrote:
> On Thu, 2004-07-08 at 21:33 +0200, Andreas Jochens wrote:
> > On 04-Jul-08 13:58, Chris Cheney wrote:
> > > I don't know if there is an actual ABI change but what it accepts is
> > > more strict so it could break building packages, whether it breaks
> > > binary compatibility though is another question.
> >
> > Yes, gcc-3.4 breaks some packackage because it is stricter.
> >
> > While recompiling my private amd64 archive with gcc-3.4.1 I found the
> > following kinds of problems with gcc-3.4 in a (small) number of
> > packages:
>
> [snip examples]
>
> > I am sure there will be more of those little problems (I still have to
> > rebuild a few thousand packages with gcc-3.4.1). These problems
> > are easy to fix. They must be fixed anyway because at some point
> > debian _will_ switch to gcc-3.4. I do not think that these little
> > problems should prevent us from using gcc-3.4 for the amd64 port.
> >
> > Regarding a possible ABI change, I suspect that there is no
> > ABI change from gcc-3.3 to gcc-3.4 until someone points me
> > to some kind of official document describing such a change.
>
> The GCC team wouldn't just have made these strictness changes
> without flagging warnings in earlier versions, would they?
Yes, they would.
GCC-3.4 has a new c++ parser. In some cases the old parser isn't capable of
diagnosing these failures. In other cases the changes are required to
correctly parse some constructs.
It's worth remembering that these changes generally remove nonstandard,
undocumented "features" that should never have worked. Besides which, adding
warnings for these cases to the old parser would risk introducing new bugs
into a stable release branch.
Paul
Reply to: