login
Header Space

 
 

Tools: GCC 3.3.3

February 24, 2004 - 7:49pm
Submitted by Jeremy on February 24, 2004 - 7:49pm.
Applications and Utilities

Version 3.3.3 of the GNU Compiler Collection was announced today, following the earlier 3.3.2 [story] by about 4 months. Gabriel Dos Reis says:

"This release is primarily a bug-fix release and the most recent release in the GCC-3.3.x series. In addition to an impressive list of bugs that have been fixed, it also contains some minor features."

The changelog lists four new minor features, "suport for --with-sysroot, support for automatic detection of executable stacks, support for SSE3 instructions, and support for local thread storage debugging under GDB on S390". Download this new release from a GCC mirror site. Read on for the full announcement.


From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To:  gcc-announce
Subject: GCC-3.3.3 is released
Date: 24 Feb 2004 20:00:01 +0100


GCC-3.3.3 is now available from sites listed at these URLs:

    http://gcc.gnu.org/mirrors.html
    http://www.gnu.org/order/ftp.html

This release is primarily a bug-fix release and the most recent release
in the GCC-3.3.x series.  In addition to an impressive list of bugs
that have been fixed, it also contains some minor features.  More
detail about this release is available at:

   http://gcc.gnu.org/gcc-3.3/changes.html#3.3.3

Lots of people contributed many fixes, back-ports and testing for this
release.  Special thanks to Eric Botcazou, Joe Buck, Richard Henderson,
Matthias Klose, Gerald Pfeifer, Andrew Pinski, Roger Sayle, and many
others (too many to name in full here).

-- 
                                                       Gabriel Dos Reis 
                                                      [email blocked]


I remember it was released on Feb 14.

February 24, 2004 - 9:20pm
Anonymous

The date on http://gcc.gnu.org/ also says Feb 14. Did they change anything after that?

Re: I remember it was released on Feb 14

February 25, 2004 - 9:03am
Anonymous

Yes, but there where problems wrt to the uploading to the FSF-mirros. A lot filenames are *+* (because of c++). The securitymeasures due to the hacks some weeks ago cause problems with such filenames. Thus, the announcement has been postponed.

What about 3.4?

February 24, 2004 - 11:37pm
Anonymous

Not to be ingrateful, but I'm really looking forward to the release of 3.4, with its supposedly improved compiler error messages.

Anyone know when that one's likely to be released?

release date

February 25, 2004 - 4:30am
Anonymous

Is not release date supposed to be one month after creation of the branch? Branch creation took place earlier this month, so 3.4 should not be long now AFAIK.

re: release date

February 25, 2004 - 8:08am
Anonymous

I would have thought that one month would be ambitious - there are 87 regressions marked for 3.4.0 (see http://gcc.gnu.org/ml/gcc/2004-02/msg00412.html) which is a fair number. Also, 3.3.x is trundling along well and getting nice and stable (finally). How many distros use 3.3.x in release by default?

re: re: release date

February 25, 2004 - 8:10am
Anonymous

To be more precise - "The release will occur two months after the creation of the branch" (from http://gcc.gnu.org/develop.html, under Methodology).

Default in distros

February 25, 2004 - 10:16am

3.3.3 is default compiler in Slackware since Feb 15.

--
:wq

Slackware 9.1

February 26, 2004 - 7:02pm

Just to let you know, I compiled gcc-3.3.3 on a Dual MP system running 2.6.3 on slackware 9.1. Compiled with gcc-3.3.2. Build a package and put it on my other systems as well (also running 9.1). Works wonderfully! I'm quite impressed with this release. And so you know, the latest slack is using the Feb 14th release.

So yes, it compiles and runs great. Compiled 2.6.3 on 2 systems with different configs...both work like a charm. I'd have to say its fairly stable.

The new parser is supposedly

February 25, 2004 - 6:12pm
Anonymous

The new parser is supposedly more correct, but from what I've seen they are often excessively verbose and probably not much better, if not worse. I'd personally like to see carot (^) markers below an error/warning and a description for each, instead of huge text dumps with line numbers.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
speck-geostationary