public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jfrech.bugzilla at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/97430] New: internal compiler error: in verify_ctor_sanity, at cp/constexpr.c:3884
Date: Wed, 14 Oct 2020 23:43:03 +0000 [thread overview]
Message-ID: <bug-97430-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97430
Bug ID: 97430
Summary: internal compiler error: in verify_ctor_sanity, at
cp/constexpr.c:3884
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jfrech.bugzilla at gmail dot com
Target Milestone: ---
Possible duplicate of Bug 96241.
The following one-line source file triggers an ICE with `-std=c++17`:
int main(){[](){enum E{F};struct{E e{F};}p[1]{};return p->e;};}
% g++ -std=c++17 ice.cpp
ice.cpp: In static member function ‘static constexpr main()::<lambda()>::E
main()::<lambda()>::_FUN()’:
ice.cpp:1:61: in ‘constexpr’ expansion of ‘0->main()::<lambda()>()’
ice.cpp:1:61: internal compiler error: in verify_ctor_sanity, at
cp/constexpr.c:3884
1 | int main(){[](){enum E{F};struct{E e{F};}p[1]{};return p->e;};}
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-10/README.Bugs> for instructions.
next reply other threads:[~2020-10-14 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 23:43 jfrech.bugzilla at gmail dot com [this message]
2020-10-14 23:54 ` [Bug c++/97430] [10/11 Regression] " mpolacek at gcc dot gnu.org
2020-10-15 1:48 ` mpolacek at gcc dot gnu.org
2020-10-15 3:04 ` mpolacek at gcc dot gnu.org
2020-10-15 4:03 ` mpolacek at gcc dot gnu.org
2020-10-15 4:07 ` mpolacek at gcc dot gnu.org
2020-10-15 7:25 ` rguenth at gcc dot gnu.org
2020-10-15 14:05 ` mpolacek 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-97430-4@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).