From: Mark Mitchell <mark@codesourcery.com>
To: gcc-announce@gcc.gnu.org
Subject: GCC 3.2.1 Released
Date: Fri, 22 Nov 2002 08:43:00 -0000 [thread overview]
Message-ID: <10290000.1037982398@warlock.codesourcery.com> (raw)
The GCC 3.2.1 release is now available from the sites listed at:
http://www.gnu.org/order/ftp.html
This release contains a very large number of bug-fixes relative to
GCC 3.2, but almost no new features. See this page:
http://gcc.gnu.org/gcc-3.2/changes.html
for a more complete list of changes and this message:
http://gcc.gnu.org/ml/gcc/2002-11/msg00445.html
for a list of GNATS PRs fixed by this release.
The next release of GCC will probably be GCC 3.2.2, with more GCC 3.2
bug fixes. Not long after that, we anticipate releasing GCC 3.3, which
will have more substantive changes.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
reply other threads:[~2002-11-22 16:43 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=10290000.1037982398@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-announce@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).