The GCC 3.2.1 release is to provide a stable platform for OS distributors to use building their next OS releases. A primary objective was to stabilize the C++ ABI.
GCC 3.2.1 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
The announcement hasn’t even hit the gcc list. Was someone stalking the ftp server or what?
Cool! I guess Debian will have it by 2010 AD
Any idea if its binary compat with gcc 3.2.0?
The mention of “stabilize the c++ abi” makes me nervous.
Debian has gotten 3.* pretty quick.
Well, not if you’re using the stable release.
But hey, it’s easy, just slightly edit /etc/apt/sources.list
Is it safe? Well, I have been doing it since 1999 now… no problems what-so-ever yet!
There were a couple of obscure ABI defects uncovered, but there is a new flag (-Wabi or something) that preserves the old behavior of 3.2. In practical terms I doubt it will make any difference.
Be a peach and provide this as an update through YaST
Speaking of debian, security.debian.org has burned down. No apt-get for me 🙂
eloj@nynaeve:~$ su -c “apt-get update”
Password:
Err http://security.debian.org stable/updates/main Packages
Could not connect to security.debian.org:80 (130.89.175.34). – connect (113 No route to host)
Here’s a webcam pointed in the direction of the fire at University of Twente (www.utwente.nl, http://ns.traserv.com:8001/ispy.jpg
<em>”Cool! I guess Debian will have it by 2010 AD”</em>
That’s really unfair. Just “apt-get install gcc-3.2/unstable” and you’ll get it.
The release notes for gcc 3.2.1 are at http://gcc.gnu.org/ml/gcc/2002-11/msg00445.html
See also http://gcc.gnu.org/gcc-3.2/changes.html
I think the ABI was stabilised with the 3.2 release. The pages above report ABI bug fixes in 3.2.1 for the x86-64 architecture only.
I was stalking the ftpsite…. I’ve been waiting for this so long, I posted on forums.gentoo.org about 16 hours ago or so…
Glad to see I was not the only one though…
GCC team, rock on !
I was wondering if gcc or g++ have a special check mode where he can check at compilation time, if all declared expections of the method you use are caught or thrown in you method.
Like :
A() {
public:
t() {
B b;
b->ThisLaunchException()
}
}
Typically, java refuse compilation because A::t does not catch exception or declare throwning them.
This kind of check , can make my code better…
Cool! I guess Debian will have it by 2010 AD
Debian were waiting for 3.2.1 to start using GCC 3.x as default compiler. They can really start to implement it now.
stalking the wild asparagus