public inbox for gcc-announce@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: gcc-announce@gcc.gnu.org
Subject: GCC 4.9.0 Released
Date: Tue, 22 Apr 2014 15:04:00 -0000	[thread overview]
Message-ID: <20140422131115.GM1817@tucnak.redhat.com> (raw)

One year and one month passed from the time when the last major version
of the GNU Compiler Collection has been announced, so it is the time again
to announce a new major GCC release, 4.9.0.

GCC 4.9.0 is a major release containing substantial new
functionality not available in GCC 4.8.x or previous GCC releases.

The Local Register Allocator, introduced in GCC 4.8.0 for ia32 and
x86-64 targets only, is now used also on the Aarch64, ARM, S/390
and ARC targets by default and on PowerPC and RX targets optionally.

There have been substantial improvements to C++ devirtualization
and various scalability bottlenecks in the interprocedural optimizations
and LTO have been fixed.

Support for various C++14 additions have been added to the C++ Front End,
on the standard C++ library side the most important addition is
support for the C++11 <regex>.

GCC 4.9.0 supports the OpenMP 4.0 standard for C and C++, and a partial
implementation of the Cilk Plus extension for data and task parallelism.

Various kinds of undefined behaviors in programs can be now diagnosed at
runtime through Undefined Behavior Sanitizer.

Support for the new little-endian powerpc64le-linux platform has been added,
which defaults to the new PowerPC ELFV2 ABI.
On x86-64 and ia32, support for the AVX-512 instruction set has been
implemented.

See

 http://gcc.gnu.org/gcc-4.9/changes.html

for more information about changes in GCC 4.9.

This release is available from the FTP servers listed here:

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

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

If you encounter difficulties using GCC 4.9, please do not contact me
directly.  Instead, please visit http://gcc.gnu.org for information
about getting help.


Driving a leading free software project such as GNU Compiler Collection
would not be possible without support from its many contributors.
Not to only mention its developers but especially its regular testers
and users which contribute to its high quality.  The list of individuals
is too large to thank individually!

                 reply	other threads:[~2014-04-22 15:04 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=20140422131115.GM1817@tucnak.redhat.com \
    --to=jakub@redhat.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).