public inbox for gcc-announce@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: gcc-announce@gcc.gnu.org
Subject: GCC 3.0.3 Released
Date: Sun, 23 Dec 2001 12:53:00 -0000	[thread overview]
Message-ID: <18030000.1009140472@gandalf.codesourcery.com> (raw)
Message-ID: <20011223125300.gUhQhpa39Xk5UasjcJTX2mSELZex5jh39v0gimGmSpI@z> (raw)

The GCC 3.0.3 release is now available.

This is bug-fix release only.  This release contains fixes for
many bugs, including:

  A fix to correct an accidental change to the PowerPC ABI.
  Fixes for bad code generation on a variety of architectures.
  Improvements to the debugging information generated for C++ classes.
  Fixes for bad code generation in C++.
  A fix to avoid crashes in the C++ demangler.
  A fix to the C++ standard library to avoid buffer overflows.
  Miscellaneous improvements for a variety of architectures.

If you are using GCC 3.0.2 without problems, there is little reason
to upgrade.  However, if you are having problems, you may find
that they are fixed in GCC 3.0.3.

A large number of people contributed to this release.  Especially
helpful were:

  David Edelsohn -- for PowerPC work.
  Richard Henderson -- for back end bug fixes.
  Joseph Myers -- for documentation work.
  David O'Brien -- for FreeBSD improbements.
  Craig Rodrigues -- for identifying and fixing important bugs.

See:

  http://www.fsf.org/order/ftp.html

and:

  http://gcc.gnu.org/mirrors.html

for a list of the sites from which you may download GCC 3.0.3.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

             reply	other threads:[~2001-12-23 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  0:41 Mark Mitchell [this message]
2001-12-23 12:53 ` Mark Mitchell

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=18030000.1009140472@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).