public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/99983] [9/10 regression] ICE in bootstrap while building libstdc++
Date: Fri, 09 Apr 2021 17:10:28 +0000 [thread overview]
Message-ID: <bug-99983-4-M8ClzZKKeH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99983-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99983
--- Comment #18 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Maxim Kuvyrkov from comment #3)
> It appears to be
> ===
> commit 1c4e8a96cd695c03ff85299bf2392476feae99bb
> Author: François Dumont <fdumont@gcc.gnu.org>
> Date: Mon Jan 20 19:15:43 2020 +0100
>
> libstdc++: Fix unordered containers move constructors noexcept qualification
>
> _Hashtable move constructor is wrongly qualified as noexcept(true)
> regardless of
> _Equal and _H1 copy constructor qualifications.
> _Hashtable allocator-aware move constructor is missing its noexcept
> qualification like the depending unordered containers ones.
>
> This backport also includes the changes from r11-8062.
> ===
>
> And also confirmed on x86_64, aarch64, and aarch32.
N.B. the original patch on trunk was by François, but the backport was done by
me, with the "changes from r11-8062" which were mine and which caused the
issue. I probably should have kept them separate, so François wouldn't get
blamed.
I didn't see this PR (and that I'd caused it) until I was CC'd in comment 9.
Sorry it took so long to fix.
prev parent reply other threads:[~2021-04-09 17:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 3:48 [Bug bootstrap/99983] New: [10 " seurer at gcc dot gnu.org
2021-04-09 4:10 ` [Bug bootstrap/99983] " seurer at gcc dot gnu.org
2021-04-09 7:12 ` rguenth at gcc dot gnu.org
2021-04-09 8:03 ` mkuvyrkov at gcc dot gnu.org
2021-04-09 8:34 ` rguenth at gcc dot gnu.org
2021-04-09 8:34 ` rguenth at gcc dot gnu.org
2021-04-09 9:54 ` [Bug bootstrap/99983] [9/10 " ro at gcc dot gnu.org
2021-04-09 9:58 ` rguenth at gcc dot gnu.org
2021-04-09 12:53 ` mkuvyrkov at gcc dot gnu.org
2021-04-09 13:40 ` jakub at gcc dot gnu.org
2021-04-09 14:02 ` marxin at gcc dot gnu.org
2021-04-09 14:24 ` redi at gcc dot gnu.org
2021-04-09 14:25 ` redi at gcc dot gnu.org
2021-04-09 14:48 ` mpolacek at gcc dot gnu.org
2021-04-09 15:15 ` cvs-commit at gcc dot gnu.org
2021-04-09 16:41 ` mpolacek at gcc dot gnu.org
2021-04-09 16:42 ` cvs-commit at gcc dot gnu.org
2021-04-09 16:43 ` redi at gcc dot gnu.org
2021-04-09 17:10 ` redi at gcc dot gnu.org [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=bug-99983-4-M8ClzZKKeH@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).