diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2021-03-23 10:23:42 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2021-03-23 10:23:42 +0100 |
| commit | 3e07e7a6a7f34f0ec2f1a3e50ebc52b77de11a30 (patch) | |
| tree | 9de1e3a2da95fe61d4939efd2fba0bfa1813a0e4 /gcc/analyzer | |
| parent | a28cc94a27529b3108ea85be9ef5557a3c95791d (diff) | |
| download | gcc-3e07e7a6a7f34f0ec2f1a3e50ebc52b77de11a30.zip gcc-3e07e7a6a7f34f0ec2f1a3e50ebc52b77de11a30.tar.gz gcc-3e07e7a6a7f34f0ec2f1a3e50ebc52b77de11a30.tar.bz2 | |
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.
Diffstat (limited to 'gcc/analyzer')
0 files changed, 0 insertions, 0 deletions