From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org, gcc-announce@gcc.gnu.org
Subject: GCC 3.3.2 Released
Date: Fri, 17 Oct 2003 18:11:00 -0000 [thread overview]
Message-ID: <1066414001.25550.157.camel@doubledemon.codesourcery.com> (raw)
The GCC 3.3.2 release is now (or will soon be) available from the sites
listed at:
http://www.gnu.org/order/ftp.html
This release contains a large number of bug-fixes relative to GCC
3.3.1.
Visit:
http://gcc.gnu.org/gcc-3.3/changes.html#3.3.2
for a complete list of bugs fixed in this release.
(Thanks again to Joe Buck for preparing this list!)
I do not anticipate any further GCC 3.3.x releases; the next GCC release
will be GCC 3.4, which will contain a number of new features such as
pre-compiled headers, a new C++ parser, and improved optimizations.
It's difficult to predict a release date for GCC 3.4, but my current
best guess is March 1st, 2004.
It's possible that there will be a GCC 3.3.3, if the GCC 3.4 schedule
slips significantly.
I'd like to thank Eric Botcazou for helping to produce, backport, and
apply a number of patches in advance of this release. I'd also like to
thank everyone who fixed a bug for the GCC 3.3.2 -- a list too long to
give here!
--
Mark Mitchell <mark@codesourcery.com>
CodeSourcery, LLC
reply other threads:[~2003-10-17 18:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1066414001.25550.157.camel@doubledemon.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-announce@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).