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++/97974] New: [9/10/11 Regression] ICE tree check: expected overload, have function_decl in get_class_binding_direct, at cp/name-lookup.c:1332 Date: Tue, 24 Nov 2020 18:32:36 +0000 [thread overview] Message-ID: <bug-97974-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97974 Bug ID: 97974 Summary: [9/10/11 Regression] ICE tree check: expected overload, have function_decl in get_class_binding_direct, at cp/name-lookup.c:1332 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r8 before 20180525 : $ cat z1.cc struct { struct { operator int (); int a; }; operator int; }; $ g++-11-20201122 -c z1.cc z1.cc:6:12: internal compiler error: tree check: expected overload, have function_decl in get_class_binding_direct, at cp/name-lookup.c:1332 6 | operator int | ^~~ 0x6520ba tree_check_failed(tree_node const*, char const*, int, char const*, ...) ../../gcc/tree.c:9810 0x7fad5a tree_check(tree_node*, char const*, int, char const*, tree_code) ../../gcc/tree.h:3317 0x7fad5a get_class_binding_direct(tree_node*, tree_node*, bool) ../../gcc/cp/name-lookup.c:1332 0x8ea66b lookup_field_r ../../gcc/cp/search.c:978 0x8e904e dfs_walk_all(tree_node*, tree_node* (*)(tree_node*, void*), tree_node* (*)(tree_node*, void*), void*) ../../gcc/cp/search.c:1408 0x8e91fc lookup_member(tree_node*, tree_node*, int, bool, int, access_failure_info*) ../../gcc/cp/search.c:1121 0x8e95a0 lookup_fnfields(tree_node*, tree_node*, int, int) ../../gcc/cp/search.c:1327 0x80aada lookup_name_1 ../../gcc/cp/name-lookup.c:6587 0x80aada lookup_name(tree_node*, LOOK_where, LOOK_want) ../../gcc/cp/name-lookup.c:6665 0x811255 lookup_name(tree_node*, LOOK_want) ../../gcc/cp/name-lookup.h:294 0x811255 cp_parser_lookup_name ../../gcc/cp/parser.c:28864 0x818615 cp_parser_diagnose_invalid_type_name ../../gcc/cp/parser.c:3365 0x84a063 cp_parser_parse_and_diagnose_invalid_type_name ../../gcc/cp/parser.c:3619 0x860367 cp_parser_member_declaration ../../gcc/cp/parser.c:25456 0x82f722 cp_parser_member_specification_opt ../../gcc/cp/parser.c:25306 0x82f722 cp_parser_class_specifier_1 ../../gcc/cp/parser.c:24395 0x832159 cp_parser_class_specifier ../../gcc/cp/parser.c:24706 0x832159 cp_parser_type_specifier ../../gcc/cp/parser.c:17962 0x832d86 cp_parser_decl_specifier_seq ../../gcc/cp/parser.c:14584 0x8339f1 cp_parser_simple_declaration ../../gcc/cp/parser.c:13841
next reply other threads:[~2020-11-24 18:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-24 18:32 gscfq@t-online.de [this message] 2020-11-25 8:11 ` [Bug c++/97974] " marxin at gcc dot gnu.org 2020-11-25 8:20 ` rguenth at gcc dot gnu.org 2021-04-10 15:12 ` jason at gcc dot gnu.org 2021-04-11 3:52 ` cvs-commit at gcc dot gnu.org 2021-04-12 19:49 ` [Bug c++/97974] [9/10 " jason at gcc dot gnu.org 2021-04-29 18:42 ` cvs-commit at gcc dot gnu.org 2021-06-01 8:19 ` rguenth at gcc dot gnu.org 2022-05-27 9:43 ` [Bug c++/97974] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2023-07-07 9:13 ` rguenth 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-97974-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).