From: Mark Mitchell <mark@codesourcery.com>
To: gcc-announce@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: GCC 3.3 Released
Date: Wed, 14 May 2003 23:49:00 -0000 [thread overview]
Message-ID: <200305142345.h4ENjScJ002366@doubledemon.codesourcery.com> (raw)
The GCC 3.3 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.3, and a number of new features. See this page:
http://gcc.gnu.org/gcc-3.3/changes.html
for a more complete list of changes.
The next release of GCC will be GCC 3.3.1, which will be a bug-fix
release.
As always, there are far too many people involved in the development
and testing of GCC to name them all, but I would like to recognize a
few people whose efforts made it notably easier for me to manage this
release:
In alphabetical order:
- Joe Buck, for producing our release notes.
- Richard Henderson, for reviewing zillions of patches.
- Gerald Pfeifer, for maintaining all of the web documentation.
- Angela Thomas, for putting our CVS repository back together in
incredibly short order, after I made a mess of it.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
reply other threads:[~2003-05-14 23:49 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=200305142345.h4ENjScJ002366@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).