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 10.1 Released
Date: Thu, 7 May 2020 14:59:59 +0200	[thread overview]
Message-ID: <20200507125959.GO8462@tucnak> (raw)

A year has lapsed away since the release of last major
GCC release, more than 33 years passed since the first
public GCC release and the GCC developers survived
repository conversion from SVN to GIT earlier this year.

Today, we are glad to announce another major GCC release, 10.1.

This release makes great progress in the C++20 language support,
both on the compiler and library sides [1], some C2X enhancements,
various optimization enhancements and bug fixes, several new
hardware enablement changes and enhancements to the compiler back-ends
and many other changes.  There is even a new experimental static
analysis pass [2].

Some code that compiled successfully with older GCC versions might require
source changes, see http://gcc.gnu.org/gcc-10/porting_to.html for
details.

See

  https://gcc.gnu.org/gcc-10/changes.html

for more information about changes in GCC 10.1.

This release is available from the FTP servers listed here:

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

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

If you encounter difficulties using GCC 10.1, 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!

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

----

[1] See https://gcc.gnu.org/projects/cxx-status.html,
    and https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2020

[2] See https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10

[3] See https://my.fsf.org/civicrm/contribute/transact?reset=1&id=57


                 reply	other threads:[~2020-05-07 13:00 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=20200507125959.GO8462@tucnak \
    --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).