From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org, gcc-announce@gcc.gnu.org
Subject: GCC 3.0.2 Release
Date: Thu, 25 Oct 2001 11:43:00 -0000 [thread overview]
Message-ID: <57510000.1004034201@gandalf.codesourcery.com> (raw)
The GCC 3.0.2 release is now available. See:
http://www.gnu.org/order/ftp.html
for a list of sites from which you can download GCC 3.0.2.
Although the GNU mirror sites have the tarballs at this point, the GCC
mirror sites do not, due to an error on my part. I have uploaded the
tarballs now, and they will reach the GCC mirrors shortly.
This is a bug-fix release to correct bugs in GCC 3.0.1. If GCC 3.0.1
works well for you, there is no reason to upgrade.
Some of the changes include:
- Bad code generation during loop unrolling.
- Bad code generation by the sibling call optimization.
- Minor improvements to x86 code generation.
- Implemenation of function descriptors in C++ vtables for IA64.
Thanks to everyone who contributed, and especially to:
Neil Booth
David Edelsohn
Richard Henderson
Jan Hubicka
Jeff Law
Joseph Meyers
Nathan Sidwell
Franz Sirl
Jim Wilson
for important improvements in this release.
The GCC 3.0 branch is now unfrozen.
Yours,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
reply other threads:[~2001-10-25 11: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=57510000.1004034201@gandalf.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).