The release hasn’t been announced yet. Must be a gcc stalker out there like what happened last time here.
Andrea: The ABI in gcc 3.1 is different, so a 3.2.x series shouldn’t work unless Apple does their own work to change the ABI back to their version, which they have to maintain now.
Also, that SuSE version of 3.3 is from the 3.3 branch, it hasn’t been released yet.
Last I checked, the ABI change only affects C++ code generation ; since Apple is using Obj-C which doesn’t use that ABI, it shouldn’t break their stuff, though it might break C++-based things built through, say, Fink. But that should be fixable via a recompile anyways, unless I’m way off.
The ABI changes between 3.1 and 3.2 only affected C++ code on the x86 systems. I’ve been using GCC 3.4 on OS X 10.2.5 box with no problems; the only reason I can think that Apple is behind is that they like to double check everything before releasing them into the Development tools which are only release about every 6 months (they also have some internal patches they like to install and test).
I’m expecting 3.2 to be released with the next tools release which should be around September with the Panther release.
Jan: the precompiled header support for GCC is scheduled for the 3.4 replease. Apple has already applied them to 3.1 with the December Developement Tools; everyone, else will have to wait for the 3.4 release. (PS: Apple donated the code to the GCC team).
The GCC ABI is cross-platform, and not limited to x86. If newer versions happen to work it’s because the differences in ABI between 3.1 and 3.2 primarily consisted of corner cases, but they’re still strictly incompatible.
when will 3.3 be released?
The first pre-release is planned for early next week.
will be ever a version of gcc 3.2.x for mac os x intead of 3.1? could we recompile 3.2.x andmake it works under project builder?
I already have it in my SuSE Linux!
[root@elvis i586]# ls | grep gcc
gcc-c++-3.3-23.i586.rpm
gcc-g77-3.3-23.i586.rpm
gcc-info-3.3-23.i586.rpm
gcc-java-3.3-23.i586.rpm
gcc-objc-3.3-23.i586.rpm
gcc-3.3-23.i586.rpm
libgcc-3.3-23.i586.rpm
When will ObjC++ be included in the main gcc ???
The release hasn’t been announced yet. Must be a gcc stalker out there like what happened last time here.
Andrea: The ABI in gcc 3.1 is different, so a 3.2.x series shouldn’t work unless Apple does their own work to change the ABI back to their version, which they have to maintain now.
Also, that SuSE version of 3.3 is from the 3.3 branch, it hasn’t been released yet.
Last I checked, the ABI change only affects C++ code generation ; since Apple is using Obj-C which doesn’t use that ABI, it shouldn’t break their stuff, though it might break C++-based things built through, say, Fink. But that should be fixable via a recompile anyways, unless I’m way off.
Does anybody know how to use precompiled headers with gcc 3.2 e.g. to speed up compiletime for projects using wxWindows?
The ABI changes between 3.1 and 3.2 only affected C++ code on the x86 systems. I’ve been using GCC 3.4 on OS X 10.2.5 box with no problems; the only reason I can think that Apple is behind is that they like to double check everything before releasing them into the Development tools which are only release about every 6 months (they also have some internal patches they like to install and test).
I’m expecting 3.2 to be released with the next tools release which should be around September with the Panther release.
Jan: the precompiled header support for GCC is scheduled for the 3.4 replease. Apple has already applied them to 3.1 with the December Developement Tools; everyone, else will have to wait for the 3.4 release. (PS: Apple donated the code to the GCC team).
Precompiled headers will be a feature of gcc 3.4 – so you have to wait.
The GCC ABI is cross-platform, and not limited to x86. If newer versions happen to work it’s because the differences in ABI between 3.1 and 3.2 primarily consisted of corner cases, but they’re still strictly incompatible.