public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iii at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100853] New: internal compiler error: in cp_tree_equal, at cp/tree.c:4148 Date: Tue, 01 Jun 2021 11:01:51 +0000 [thread overview] Message-ID: <bug-100853-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100853 Bug ID: 100853 Summary: internal compiler error: in cp_tree_equal, at cp/tree.c:4148 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iii at linux dot ibm.com Target Milestone: --- $ cat cp-tree-equal.cpp typedef struct a *b; template <typename> struct c { d({ b *e; __typeof (*({ __typeof *e f; f} )).g const f (({ __typeof (*({ int h; f} )).g const f ( $ gcc/cc1plus -fno-PIE -g -O2 -fno-checking -gtoggle -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables cp-tree-equal.cpp ... cp-tree-equal.cpp:8:37: internal compiler error: in cp_tree_equal, at cp/tree.c:4148 8 | f} )).g const f ( | ^ 0x7062e9 cp_tree_equal(tree_node*, tree_node*) ../../gcc/cp/tree.c:4148 0xbd1d3e cp_tree_equal(tree_node*, tree_node*) ../../gcc/cp/tree.c:4138 0xbd1d3e cp_tree_equal(tree_node*, tree_node*) ../../gcc/cp/tree.c:4138 0xbd1d3e cp_tree_equal(tree_node*, tree_node*) ../../gcc/cp/tree.c:4138 0xbd1d3e cp_tree_equal(tree_node*, tree_node*) ../../gcc/cp/tree.c:4138 0xbdc784 structural_comptypes ../../gcc/cp/typeck.c:1491 0xae2ffc check_local_shadow ../../gcc/cp/name-lookup.c:3264 0xae2ffc do_pushdecl ../../gcc/cp/name-lookup.c:3773 0xae39b4 pushdecl(tree_node*, bool) ../../gcc/cp/name-lookup.c:3852 0xa3995e start_decl(cp_declarator const*, cp_decl_specifier_seq*, int, tree_node*, tree_node*, tree_node**) ../../gcc/cp/decl.c:5591 0xb2dd61 cp_parser_init_declarator ../../gcc/cp/parser.c:21802 0xb093cd cp_parser_simple_declaration ../../gcc/cp/parser.c:14487 0xb0b0a9 cp_parser_declaration_statement ../../gcc/cp/parser.c:13622 0xb0bc0b cp_parser_statement ../../gcc/cp/parser.c:11848 0xb0ce0e cp_parser_statement_seq_opt ../../gcc/cp/parser.c:12215 0xb0cee8 cp_parser_compound_statement ../../gcc/cp/parser.c:12164 0xb10473 cp_parser_statement_expr ../../gcc/cp/parser.c:5142 0xb10473 cp_parser_primary_expression ../../gcc/cp/parser.c:5549 0xb11b80 cp_parser_postfix_expression ../../gcc/cp/parser.c:7528 0xb243af cp_parser_unary_expression ../../gcc/cp/parser.c:8849 Found when reducing a testcase for another problem.
next reply other threads:[~2021-06-01 11:01 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-01 11:01 iii at linux dot ibm.com [this message] 2021-06-01 11:03 ` [Bug c++/100853] " iii at linux dot ibm.com 2021-08-12 23:17 ` [Bug c++/100853] [11/12 Regression] " pinskia at gcc dot gnu.org 2021-08-12 23:17 ` pinskia at gcc dot gnu.org 2022-01-20 12:59 ` rguenth at gcc dot gnu.org 2022-01-31 14:53 ` [Bug c++/100853] [11/12 Regression] internal compiler error: in cp_tree_equal, at cp/tree.c:4148 since r11-2275-g5324a3e621d9a2ee marxin at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2023-05-29 10:05 ` [Bug c++/100853] [11/12/13/14 " jakub 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-100853-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).