From: Pramesh Gupta <pramesh.gupta94@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: GCC 12.1 Released
Date: Fri, 6 May 2022 23:35:56 +0530 [thread overview]
Message-ID: <CANDCUQ-2aX19hPfRV64aYkLn8XqWQ7WvREn0HT1P+ieFXmO1rg@mail.gmail.com> (raw)
In-Reply-To: <p3p5oo2-3221-p179-5547-o250q2p5r8sn@fhfr.qr>
UNSUBSCRIBE
On Fri, 6 May 2022, 14:57 Richard Biener via gcc-announce, <
gcc-announce@gcc.gnu.org> wrote:
>
> The GCC developers are proud to announce another major GCC release, 12.1.
>
> This year we celebrated the 35th anniversary of the first GCC beta release
> and this month we will celebrate 35 years since the GCC 1.0 release!
>
> This release deprecates support for the STABS debugging format and
> introduces support for the CTF debugging format [1]. The C and C++
> frontends continue to advance with extending support for features
> in the upcoming C2X and C++23 standards and the C++ standard library
> improves support for the experimental C++20 and C++23 parts.
> The Fortran frontend now fully supports TS 29113 for interoperability with
> C.
>
> GCC now understands clangs __builtin_shufflevector extension making
> it easier to share generic vector code. Starting with GCC 12
> vectorization is enabled at the -O2 optimization level using the
> very-cheap cost model which puts extra constraints on code size expansion.
>
> On the security side GCC can now initialize stack variables implicitly
> using -ftrivial-auto-var-init to help tracking down and mitigating
> uninitialized stack variable flaws. The C and C++ frontends now support
> __builtin_dynamic_object_size compatible with the clang extension.
> The x86 backend gained mitigations against straight line speculation
> with -mharden-sls. The experimental Static Analyzer gained uninitialized
> variable use detection and many other improvements.
>
> The x86 backend gained support for AVX512-FP16 via _Float16.
> The BPF backend now supports CO-RE, the RISC-V backend gained support
> for many new ISA extensions.
>
> Some code that compiled successfully with older GCC versions might require
> source changes, see http://gcc.gnu.org/gcc-12/porting_to.html for
> details.
>
> See
>
> https://gcc.gnu.org/gcc-12/changes.html
>
> for more information about changes in GCC 12.1.
>
> This release is available from the WWW and FTP servers listed here:
>
> https://sourceware.org/pub/gcc/releases/gcc-12.1.0/
> https://gcc.gnu.org/mirrors.html
>
> The release is in the gcc-12.1.0/ subdirectory.
>
> If you encounter difficulties using GCC 12.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!
>
> ----
>
> [1] See https://ctfstd.org/
>
prev parent reply other threads:[~2022-05-06 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 8:48 Richard Biener
2022-05-06 11:21 ` unsubscribe Peter Quinger
2022-05-06 18:05 ` Pramesh Gupta [this message]
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=CANDCUQ-2aX19hPfRV64aYkLn8XqWQ7WvREn0HT1P+ieFXmO1rg@mail.gmail.com \
--to=pramesh.gupta94@gmail.com \
--cc=gcc@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).