public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91807] [9/10/11 Regression] std::variant with multiple identical types assignment fail to compile
Date: Thu, 02 Jul 2020 19:25:53 +0000 [thread overview]
Message-ID: <bug-91807-4-yWy4fWQeyE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91807-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91807
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Ville Voutilainen
<ville@gcc.gnu.org>:
https://gcc.gnu.org/g:9cba1b9a6333dcc6623865b7a0ed4d57cec4088e
commit r10-8418-g9cba1b9a6333dcc6623865b7a0ed4d57cec4088e
Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Thu Jul 2 22:16:39 2020 +0300
PR libstdc++/91807
PR libstdc++/91807
* include/std/variant
(_Copy_assign_base::operator=(const _Copy_assign_base&):
Do the move-assignment from a temporary so that the temporary
is constructed with an explicit index.
* testsuite/20_util/variant/91807.cc: New.
(cherry picked from commit dbca7a69f276e4829354f87f2747ebff36f6090e)
next prev parent reply other threads:[~2020-07-02 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91807-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug libstdc++/91807] [9/10 " jakub at gcc dot gnu.org
2020-04-01 8:31 ` rguenth at gcc dot gnu.org
2020-04-24 0:16 ` redi at gcc dot gnu.org
2020-07-01 17:22 ` [Bug libstdc++/91807] [9/10/11 " ville.voutilainen at gmail dot com
2020-07-02 19:17 ` cvs-commit at gcc dot gnu.org
2020-07-02 19:25 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-02 19:44 ` cvs-commit at gcc dot gnu.org
2020-07-02 19:45 ` ville.voutilainen at gmail dot com
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-91807-4-yWy4fWQeyE@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).