public inbox for gcc-announce@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc-announce@gcc.gnu.org, gcc@gcc.gnu.org, info-gnu@gnu.org
Subject: GCC 13.1 Released
Date: Wed, 26 Apr 2023 08:20:42 +0000 (UTC)	[thread overview]
Message-ID: <nycvar.YFH.7.77.849.2304260818480.4466@jbgna.fhfr.qr> (raw)

The GCC developers are proud to announce a new major GCC release, 13.1.

This release integrates a frontend for the Modula-2 language which
was previously available separately and lays foundation for a
frontend for the Rust language which will be available in a future
release.

Support for emitting the STABS debugging format was removed.  GCC
supports DWARF in almost all configurations.

The C frontend got support for several C23 features, the C++ frontend
for C++23 features.  The C++ standard library experimental support for
C++20 and C++23 was enhanced.  For the C family of languages you can now
use -fstrict-flex-arrays[=level] to control the behavior for the various
legacy forms of specifying flexible array members.

GCCs static analyzer has been greatly improved with 20 new diagnostic
kinds.

Link-time optimization now makes automatic use of GNU makes jobserver
when that supports named pipes which it does starting with version 4.4.
It is no longer required to alter makefiles.

Support for new CPU features in the ARM, x86 family, RISC-V and LoongArch
were added.  Notably RISC-V supports vector intrinsics as specified in
the 0.11 specification and OpenMP/OpenACC offloading to AMD Instinct MI200
series devices has been added.

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

See

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

for more information about changes in GCC 13.1.

This release is available from the WWW and FTP servers listed here:

 https://sourceware.org/pub/gcc/releases/gcc-13.1.0/
 https://gcc.gnu.org/mirrors.html

The release is in the gcc-13.1.0/ subdirectory.

If you encounter difficulties using GCC 13.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 GCC would not be possible
without support from its many contributors.
Not only 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:[~2023-04-26  8:20 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=nycvar.YFH.7.77.849.2304260818480.4466@jbgna.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-announce@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=info-gnu@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).