This GCC release is based on the GCC 3.1 sourcebase, and thus has all the changes in the GCC 3.1 series. In addition, GCC 3.2 has a number of C++ ABI fixes which make its C++ compiler generate binary code which is incompatible with the C++ compilers found in earlier GCC releases, including GCC 3.1 and GCC 3.1.1.
GCC 3.2 Released
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
So GCC 3.2 is finally released. This means as soon as it’s throughly tested by the Gentoo folks, Gentoo 1.4 is going to be released. At least, thats what the topic in #Gentoo says:
“21:45:55 -!- Topic for #Gentoo: Gentoo Linux || please test pcmcia-cs-3.2.0 || t-shirts, caps and other goodies: http://cafepress.com/gentoolinux || List of IRC channels @ http://www.gentoo.org! || Check out Gentoo stats: http://gentoo.iq-computing.de || Coming soon: Gentoo 1.4! (gcc 3.2) *crowd goes wild* || WARNING: 1.4_beta ONLY for devs and testers, b0rk@ge garanteed!! || yes, we know gcc 3.2 is out
|| 1.4 will be out after we test gcc and friends”
every time I hear a new release…and they seem to be fast and furious since 3.0, they seem to improove a little each time on c++ speed.
Maybe this will allow the next FreeBSD (5.x) to have all the ports collection compiled with GCC 3.2 (the problem is no backwards compat).
So the gcc that ships with Jaguar is using an obsolete ABI… that’s just great
This is exactly why I can’t wait for gentoo 1.4. Although I just moved, so I’m without Internet at home, so I guess I can wait for gentoo since I can’t really install it without a fat pipe to suck all the source over.
Indeed, was about time..
Yes, indeed.
And it seems that Apple won’t sync with gcc-3.3 either. According to a mail from an Apple s/w engineer in the gcc mailing list, they intend to NOT use the codebase of gcc-3.3 for their next MacOS release.
AFAIK is Apples gcc a gcc-3.x, but with a patched g++-2.95.x (at least is was before Jaguar). So ABI really doesn’t count …
And yes, Apple was aware of the ABI change.
AFAIK is Apples gcc a gcc-3.x, but with a patched g++-2.95.x (at least is was before Jaguar). So ABI really doesn’t count …
And yes, Apple was aware of the ABI change.
A little research would have told you that Jaguar is using gcc 3.1. Check it out yourself: http://www.apple.com/macosx
True enough, a little bit more research would have helped
But I’m not sure/convinced whether Apple’s gcc-3.1 still doesn’t use an old version of G++ …
E.g. Stan Shebs (an Apple Engineer, working on Objective-C and ObjC++) has some problems in porting Apple’s ObjC++-changes into the FSF version of GCC. Specifically he has some trouble of integrating the ObjC class hierarchy into C++ (IIRC), so there are obviously quite some major differences in Apple G++ and FSF G++.
>>So the gcc that ships with Jaguar is using an obsolete ABI… that’s just great
What does it matter? Who do they to be binary compatible with?
I’ll need to recompile about everything, from bootstrap to kde and mozilla to have it faster… hmm… do I have 4 days to waste ? Yes
Okay, someone tells me how to do it, I’m go
Hi folks,
I’ve seen floating around some numbers on performance improvements between gcc-2.95 and 3.x on Intel and PowerPC systems; does anyone have information on how much better GCC does on SPARC?
Yours truly,
Jeffrey Boulier
>>So the gcc that ships with Jaguar is using an obsolete ABI… that’s just great
What does it matter? Who do they to be binary compatible with?
Themselves if they ever move to a newer gcc
Since there is a *major* discontinuity in ABI, why not
release 3.2 as 4.0. This would signal a *major* change
to unsuspecting users. I my experience such a *major*
change would require a bump in the major version number.
Regards,
Ray
gcc has always been ABI incompatible when it comes to C++ between its minor versions.
Gcc 3.1 was supposed to be the one with a “stable” ABI, that
also were compatible with other compilers, but bugs were found. Hopefully there is no bugs or othere caveats in the ABI in gcc 3.2, then we will probably see a long line of gcc minor versions that are backewards compatible
Check the changes file – it says everything.
3.2 is minor bug update compare to 3.1.1 . They wouldn’t bother with new version if it wasn’t ABI compatibility problem.
Better wait for gcc 3.3 – this one will have better optimizer and will not change ABI again.
Wich will mean stability and a good way to make the migration for this new and faster gcc way more easy. Because recompiling a whole system time and time again everytime the gcc team decides to change the ABI sucks…
Even for big names has RedHat, Mandrake & SuSe incompatibility between gcc3.x releases might(or are) a major pain (you know where) .. since all of them era interested in creating their binary packages with a better & faster compiler…