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 c++/99650] ICE when trying to form reference to void in structured binding
Date: Thu, 22 Apr 2021 16:52:05 +0000 [thread overview]
Message-ID: <bug-99650-4-gbMQgYI0GA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99650-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99650
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:6132dc70413163b96955a3ebca33c849eb2eb88e
commit r8-10899-g6132dc70413163b96955a3ebca33c849eb2eb88e
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Mar 23 10:23:42 2021 +0100
c++: Diagnose references to void in structured bindings [PR99650]
We ICE on the following testcase, because std::tuple_element<...,...>::type
is void and for structured bindings we therefore need to create
void & or void && which is invalid. We created such REFERENCE_TYPE and
later ICEd in the middle-end.
The following patch fixes it by diagnosing that.
2021-03-23 Jakub Jelinek <jakub@redhat.com>
PR c++/99650
* decl.c (cp_finish_decomp): Diagnose void initializers when
using tuple_element and get.
* g++.dg/cpp1z/decomp55.C: New test.
(cherry picked from commit d5e379e3fe19362442b5d0ac608fb8ddf67fecd3)
next prev parent reply other threads:[~2021-04-22 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 17:47 [Bug c++/99650] New: " csaba_22 at yahoo dot co.uk
2021-03-18 18:22 ` [Bug c++/99650] " jakub at gcc dot gnu.org
2021-03-18 18:31 ` mpolacek at gcc dot gnu.org
2021-03-18 19:08 ` jakub at gcc dot gnu.org
2021-03-18 20:51 ` csaba_22 at yahoo dot co.uk
2021-03-23 9:24 ` cvs-commit at gcc dot gnu.org
2021-03-30 22:41 ` cvs-commit at gcc dot gnu.org
2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:52 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-22 17:11 ` jakub at gcc dot gnu.org
2021-09-11 14:23 ` pinskia at gcc dot gnu.org
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-99650-4-gbMQgYI0GA@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).