public inbox for
 help / color / mirror / Atom feed
From: Jakub Jelinek <>
Subject: GCC 8.1 Released
Date: Wed, 02 May 2018 12:33:00 -0000	[thread overview]
Message-ID: <20180502121545.GU8577@tucnak> (raw)

We are proud to announce the next, major release of the
GNU Compiler Collection.

Are you tired of your existing compilers?
Want fresh new language features and better optimizations?
Make your day with the new GCC 8.1!

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

The C++ front-end now has experimental support for some parts of the
upcoming C++2a draft, with the -std=c++2a and -std=gnu++2a options, and the
libstdc++ library has some further C++17 and C++2a draft library features
implemented too.

This releases features significant improvements in the emitted diagnostics,
including improved locations, location ranges and fix-it hints (especially
in the C++ front-end), and various new warnings have been added.

Profile driven optimizations have been significantly improved, on x86
functions are now split into hot and cold regions by default.  The link time
optimizations now have a new way of emitting the DWARF debug information,
which makes LTO optimized code more debuggable.  New loop optimizers have
added and existing improved and some, like -ftree-loop-distribution,
-floop-unroll-and-jam and -floop-interchange have been enabled by default at

The AArch64 target now supports the Scalable Vector Extension, which
features vectors with runtime determined number of elements.

Some code that compiled successfully with older GCC versions might require
source changes, see for


for more information about changes in GCC 8.1.

This release is available from the FTP servers listed here:

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

If you encounter difficulties using GCC 8.1, please do not contact me
directly.  Instead, please visit 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!

Please consider a donation to the GNU Toolchain Fund to support the
continued development of GCC!

                 reply	other threads:[~2018-05-02 12:33 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 \
    --in-reply-to=20180502121545.GU8577@tucnak \ \ \

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