public inbox for
 help / color / mirror / Atom feed
From: Jakub Jelinek <>
Subject: GCC 4.6.0 Released
Date: Mon, 28 Mar 2011 13:34:00 -0000	[thread overview]
Message-ID: <> (raw)

The GNU Compiler Collection version 4.6.0 has been released.

GCC 4.6.0 is a major release, containing substantial new functionality
not available in GCC 4.5.x or previous GCC releases.

The "link-time optimization" framework introduced in GCC 4.5.0 has been
significantly improved in this release, it is now possible to compile
very large applications like Mozilla or GCC itself with LTO.
GCC can now partially inline functions, inlining just hot short path
to exit and keeping the rest of the function out of line.
Support for the upcoming C++0x standard has been notably improved,
Fortran 2003 and 2008 has been greatly extended and many other frontends
undergone substantial changes as well.
Many other improvements have been added and more than thousand of bugs
have been fixed in various parts of the compiler collection.


for more information about changes in GCC 4.6.0.

This release is available from the FTP servers listed here:

The release is in gcc/gcc-4.6.0/ subdirectory.

If you encounter difficulties using GCC 4.6, please do not contact me
directly.  Instead, please visit for information
about getting help.

As always, a vast number of people contributed to this GCC releases --
far too many to thank individually!

                 reply	other threads:[~2011-03-28 13:34 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).