GCC 7.1 news item and blog post

[arunthomas]

GCC 7.1 is out with RISC-V support. We should create a news item.

We should also see if we can have @palmer-dabbelt do a blog post.

From: Jakub Jelinek <jakub@redhat.com>
Subject: GCC 7.1 Released
Date: 3 May 2017 at 3:57:28 AM GMT+12
To: gcc@gcc.gnu.org
Reply-To: Jakub Jelinek <jakub@redhat.com>

We are proud to announce the next, major release of the
GNU Compiler Collection, 7.1.  This year we celebrated the 30th
anniversary of the first GCC beta release and this month
we will celebrate 30 years since the GCC 1.0 release.

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

The C++ frontend now has experimental support for all of the current C++17
draft, with the -std=c++1z and -std=gnu++1z options, and the libstdc++
library has most of the C++17 draft library features implemented too.

This releases features various improvements in the emitted diagnostics,
including improved locations, location ranges, suggestions for misspelled
identifiers, option names, fix-it hints and various new warnings
have been added.

The optimizers have been improved, with improvements appearing in all of
intra- and inter-procedural optimizations, link time optimizations and
various target backends, including, but not limited to, additions of store
merging pass, code hoisting optimization, loop splitting, and
shrink wrapping improvements.

The Address Sanitizer can now report uses of variables after leaving their
scope.  GCC now can be configured for OpenMP 4.5 offloading to NVidia PTX
GPGPUs.

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

See

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

for more information about changes in GCC 7.1.

This release is available from the FTP servers listed here:

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

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

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

[palmer-dabbelt]

How do I do blog posts?

[mgielda]

I think it would be best to write it up in a Google Drive doc for now, we can then transfer it to the website.

[arunthomas]

You can just push a markdown file to the riscv-mktg repo if that's easier.

On Wed, May 3, 2017 at 12:06 PM Michael Gielda notifications@github.com wrote:

I think it would be best to write it up in a Google Drive doc for now, we can then transfer it to the blog.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/riscv/riscv-mktg/issues/39#issuecomment-298957722, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC0sFHC1M8tQSonTIFtZ5T-QwfhS8Txks5r2KYcgaJpZM4NPlEo .