public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95672] New: ICE in cxx_incomplete_type_diagnostic, at cp/typeck2.c:584
Date: Sun, 14 Jun 2020 12:48:49 +0000 [thread overview]
Message-ID: <bug-95672-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95672
Bug ID: 95672
Summary: ICE in cxx_incomplete_type_diagnostic, at
cp/typeck2.c:584
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: haoxintu at gmail dot com
Target Milestone: ---
$cat bug.cc
struct g_class : decltype (auto) ... { } ;
$g++ bug.cc
bug.cc:1:35: internal compiler error: in cxx_incomplete_type_diagnostic, at
cp/typeck2.c:584
1 | struct g_class : decltype (auto) ... { } ;
| ^~~
0x5cef74 cxx_incomplete_type_diagnostic(unsigned int, tree_node const*,
tree_node const*, diagnostic_t)
../../gcc/cp/typeck2.c:584
0x77b9af cxx_incomplete_type_diagnostic(tree_node const*, tree_node const*,
diagnostic_t)
../../gcc/cp/cp-tree.h:7705
0x77b9af complete_type_or_maybe_complain(tree_node*, tree_node*, int)
../../gcc/cp/typeck.c:156
0x77b9af complete_type_or_else(tree_node*, tree_node*)
../../gcc/cp/typeck.c:166
0x685881 xref_basetypes(tree_node*, tree_node*)
../../gcc/cp/decl.c:15099
0x6edfe9 cp_parser_class_head
../../gcc/cp/parser.c:24717
0x6edfe9 cp_parser_class_specifier_1
../../gcc/cp/parser.c:23874
0x6ee273 cp_parser_class_specifier
../../gcc/cp/parser.c:24248
0x6ee273 cp_parser_type_specifier
../../gcc/cp/parser.c:17762
0x6ef092 cp_parser_decl_specifier_seq
../../gcc/cp/parser.c:14410
0x6efbb1 cp_parser_simple_declaration
../../gcc/cp/parser.c:13664
0x7159c6 cp_parser_declaration
../../gcc/cp/parser.c:13484
0x7160b4 cp_parser_translation_unit
../../gcc/cp/parser.c:4761
0x7160b4 c_parse_file()
../../gcc/cp/parser.c:44034
0x7de74b c_common_parse_file()
../../gcc/c-family/c-opts.c:1190
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$g++ --version
g++ (GCC) 11.0.0 20200605 (experimental)
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2020-06-14 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 12:48 haoxintu at gmail dot com [this message]
2020-06-14 16:38 ` [Bug c++/95672] " haoxintu at gmail dot com
2020-06-15 6:50 ` marxin at gcc dot gnu.org
2020-06-15 8:00 ` haoxintu at gmail dot com
2020-06-15 11:20 ` marxin at gcc dot gnu.org
2020-06-15 18:22 ` mpolacek at gcc dot gnu.org
2020-06-15 22:23 ` xerofoify at gmail dot com
2020-06-24 20:08 ` cvs-commit at gcc dot gnu.org
2020-06-24 20:14 ` jason 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-95672-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).