From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] gcc-11 enters ~arch tree
Date: Tue, 27 Apr 2021 19:22:27 +0100 [thread overview]
Message-ID: <20210427192227.3b89875d@sf> (raw)
Today gcc-11.1.0 released upstream and was added to ::gentoo as:
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc068d96fb49e308456cbe944fb29b1f78e6ad5c
User-visible changes are nicely described in upstream porting doc:
https://gcc.gnu.org/gcc-11/porting_to.html
A few highlights I personally encountered are:
- use -std=gnu++17 instead of -std=gnu++14
- ordered pointer comparison with integer (like int *p; 'p > 0')
- dynamic exception specifications
- gcc now enforces that comparison objects be invocable as const
- header dependency changes
On top of that:
- -fipa-modref (enabled by default) might expose latent bugs in existing
programs. -fno-ipa-modref should be a quick hack to check the hypothesis.
Failures don't look widespread, thus gcc-11 should be fine to use as a
default compiler.
Check out known bugs and workarounds on gcc-11 tracker:
https://bugs.gentoo.org/show_bug.cgi?id=gcc-11
Gentoo Toolchain wiki page for common fixes (nothing there so far):
https://wiki.gentoo.org/wiki/Project:Toolchain#gcc-11
As usual if you can't figure out what is wrong with your package
pull in toolchain@ to the bug and we'll get to the bottom of it.
Good luck!
--
Sergei
next reply other threads:[~2021-04-27 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 18:22 Sergei Trofimovich [this message]
2021-04-28 0:42 ` [gentoo-dev] gcc-11 enters ~arch tree Sam James
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=20210427192227.3b89875d@sf \
--to=slyfox@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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