From: Mark Mitchell <mark@codesourcery.com>
To: gcc-announce@gcc.gnu.org
Subject: GCC 3.0.1 Released [Repost]
Date: Thu, 30 Aug 2001 00:13:00 -0000 [thread overview]
Message-ID: <26550000.999155525@gandalf.codesourcery.com> (raw)
[The original copy of this announcement never made it to the list.]
GCC 3.0.1 has been released.
This release contains only critical bug-fixes from GCC 3.0. The
highlights include:
- C++ fixes for incorrect code-generation.
- Improved cross-compiling support for the C++ standard library.
- Fixes for some embedded targets that worked in GCC 2.95.3, but
not in GCC 3.0.
- Fixes for exception-handling bugs.
- A port to the S/390 architecture.
As always, numerous people contributed to the release. I would
particularly like to thank Gabriel dos Reis, David Edelsohn,
Richard Henderson, Benjamin Kosnik, Jason Merrill, Joseph Meyers,
and Nathan Sidwell for their assistance.
You can find this release at the mirror sites listed in:
http://gcc.gnu.org/mirrors.html
It will also be avilable on the usual GNU mirror sites shortly.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
reply other threads:[~2001-08-30 0:13 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=26550000.999155525@gandalf.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).