public inbox for
 help / color / mirror / Atom feed
From: Mark Mitchell <>
Subject: GCC 3.1 Released
Date: Wed, 15 May 2002 17:55:00 -0000	[thread overview]
Message-ID: <> (raw)

GCC 3.1 is now available.

In this release, we focused more on quality than new features; many
bugs were fixed.  We worked very hard to fix bugs that were introduced
in GCC 3.0, but that were not present in previous releases of the
compiler.  We also worked hard to eliminate new bugs.

We have continued to improve the standards conformance in the C, C++
and Java compilers, added support for profile-directed optimizations,
improved support for many chips used in embedded systems, added an
Ada compiler, and added support for the x86-64 architecture.

For a list of many -- but by no means all -- of the changes available
in this release, see:

I would like to thank HP for sponsoring my work as Release Manager;
that support has made it possible for me to organize this release,
and will continue to support my work as RM for some time to come.

Many people worked very hard on this release.  The following list
is woefully incomplete, but does recognize some of the people I
most appreciated while preparing this release:

  Neil Booth:
    Cleanups that will reduce the chance of future bugs.

  Robert Dewar (and ACT):
    The Ada front end.

  Richard Henderson:
    Many, many bug fixes and code reviews

  Jakub Jelinek:
    Many bug fixes.

  Geoff Keating:
    Automated regression-testing.

  David Miller:
    SPARC and Solaris bug fixes.

  Gerald Pfeifer:
    Website and documentation maintenance.

The release is available from the FTP servers listed in:

The release can be found in the file:



for more information about how to obtain and install GCC.


Mark Mitchell         
CodeSourcery, LLC     

                 reply	other threads:[~2002-05-16  0:55 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).