public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106983] New: [12/13 Regression] ICE tree check: expected class 'type', have 'exceptional' (error_mark) in type_build_dtor_call, at cp/class.cc:5794 Date: Tue, 20 Sep 2022 17:31:57 +0000 [thread overview] Message-ID: <bug-106983-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106983 Bug ID: 106983 Summary: [12/13 Regression] ICE tree check: expected class 'type', have 'exceptional' (error_mark) in type_build_dtor_call, at cp/class.cc:5794 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20220206 and 20220213 : (gcc configured with --enable-checking=yes) $ cat z1.cc // struct B {int n;}; typedef unsigned long long A; typedef union { struct B s; A a; } U; void f (A x, unsigned int b) { const U y = {.a = x}; } $ g++-13-20220918 -c z1.cc z1.cc:5:12: error: field 's' has incomplete type 'B' 5 | struct B s; | ^ z1.cc:5:10: note: forward declaration of 'struct B' 5 | struct B s; | ^ z1.cc: In function 'void f(A, unsigned int)': z1.cc:10:22: internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in type_build_dtor_call, at cp/class.cc:5794 10 | const U y = {.a = x}; | ^ 0x6fc42b tree_class_check_failed(tree_node const*, tree_code_class, char const*, int, char const*) ../../gcc/tree.cc:8877 0x82fed0 tree_class_check(tree_node*, tree_code_class, char const*, int, char const*) ../../gcc/tree.h:3643 0x82fed0 type_build_dtor_call(tree_node*) ../../gcc/cp/class.cc:5794 0xb49106 split_nonconstant_init_1 ../../gcc/cp/typeck2.cc:600 0xb4ac4b split_nonconstant_init(tree_node*, tree_node*) ../../gcc/cp/typeck2.cc:739 0x8c1c71 check_initializer ../../gcc/cp/decl.cc:7453 0x8f0f4a cp_finish_decl(tree_node*, tree_node*, bool, tree_node*, int) ../../gcc/cp/decl.cc:8449 0xa244b3 cp_parser_init_declarator ../../gcc/cp/parser.cc:22997 0x9f7d82 cp_parser_simple_declaration ../../gcc/cp/parser.cc:15413 0x9f9939 cp_parser_declaration_statement ../../gcc/cp/parser.cc:14494 0x9f9feb cp_parser_statement ../../gcc/cp/parser.cc:12571 0x9fb114 cp_parser_statement_seq_opt ../../gcc/cp/parser.cc:12983 0x9fb1f7 cp_parser_compound_statement ../../gcc/cp/parser.cc:12935 0xa231a0 cp_parser_function_body ../../gcc/cp/parser.cc:25285 0xa231a0 cp_parser_ctor_initializer_opt_and_function_body ../../gcc/cp/parser.cc:25336 0xa2381a cp_parser_function_definition_after_declarator ../../gcc/cp/parser.cc:31480 0xa24d5c cp_parser_function_definition_from_specifiers_and_declarator ../../gcc/cp/parser.cc:31397 0xa24d5c cp_parser_init_declarator ../../gcc/cp/parser.cc:22735 0x9f7d82 cp_parser_simple_declaration ../../gcc/cp/parser.cc:15413 0xa2c49f cp_parser_declaration ../../gcc/cp/parser.cc:15099
next reply other threads:[~2022-09-20 17:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 17:31 gscfq@t-online.de [this message] 2022-09-20 18:28 ` [Bug c++/106983] " mpolacek at gcc dot gnu.org 2022-09-20 18:28 ` mpolacek at gcc dot gnu.org 2022-09-20 18:31 ` pinskia at gcc dot gnu.org 2022-09-20 18:38 ` mpolacek at gcc dot gnu.org 2022-09-23 0:24 ` cvs-commit at gcc dot gnu.org 2022-09-23 0:57 ` 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-106983-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: linkBe 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).