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++/109319] New: [13 Regression] ICE in build_min_non_dep_op_overload, at cp/tree.cc:3793 Date: Tue, 28 Mar 2023 18:53:21 +0000 [thread overview] Message-ID: <bug-109319-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109319 Bug ID: 109319 Summary: [13 Regression] ICE in build_min_non_dep_op_overload, at cp/tree.cc:3793 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 20221106 and 20221120, with -std=c++23 : (follow-up of pr108437) $ cat z1.cc struct S { static int operator[] (int x) { int a[2]; return a[x]; } }; template<class T> int f () { S s; ++s[0,1]; return 0; } $ cat z2.cc struct S { static int operator[] (int x) { int a[2]; return a[x]; } }; template<class T> int f () { S s; ++s[1,0]; return 0; } $ g++-13-20230326 -c z1.cc -std=c++23 z1.cc: In function 'int f()': z1.cc:8:6: warning: top-level comma expression in array subscript changed meaning in C++23 [-Wcomma-subscript] 8 | ++s[0,1]; | ^ z1.cc:8:10: internal compiler error: in build_min_non_dep_op_overload, at cp/tree.cc:3793 8 | ++s[0,1]; | ^ 0x8de226 build_min_non_dep_op_overload(tree_node*, tree_node*, tree_node*, vec<tree_node*, va_gc, vl_embed>*) ../../gcc/cp/tree.cc:3793 0x7ad99d grok_array_decl(unsigned int, tree_node*, tree_node*, vec<tree_node*, va_gc, vl_embed>**, int) ../../gcc/cp/decl2.cc:569 0x843ca4 cp_parser_postfix_open_square_expression ../../gcc/cp/parser.cc:8223 0x856671 cp_parser_postfix_expression ../../gcc/cp/parser.cc:7814 0x86a60f cp_parser_unary_expression ../../gcc/cp/parser.cc:9141 0x83e79f cp_parser_cast_expression ../../gcc/cp/parser.cc:10045 0x86a707 cp_parser_unary_expression ../../gcc/cp/parser.cc:9055 0x83e79f cp_parser_cast_expression ../../gcc/cp/parser.cc:10045 0x83f07f cp_parser_binary_expression ../../gcc/cp/parser.cc:10147 0x83fa74 cp_parser_assignment_expression ../../gcc/cp/parser.cc:10490 0x8411b2 cp_parser_expression ../../gcc/cp/parser.cc:10660 0x844837 cp_parser_expression_statement ../../gcc/cp/parser.cc:12816 0x851cbc cp_parser_statement ../../gcc/cp/parser.cc:12596 0x852d54 cp_parser_statement_seq_opt ../../gcc/cp/parser.cc:12967 0x852e0f cp_parser_compound_statement ../../gcc/cp/parser.cc:12919 0x873958 cp_parser_function_body ../../gcc/cp/parser.cc:25335 0x873958 cp_parser_ctor_initializer_opt_and_function_body ../../gcc/cp/parser.cc:25386 0x873e16 cp_parser_function_definition_after_declarator ../../gcc/cp/parser.cc:32012 0x874f90 cp_parser_function_definition_from_specifiers_and_declarator ../../gcc/cp/parser.cc:31929 0x874f90 cp_parser_init_declarator ../../gcc/cp/parser.cc:22789
next reply other threads:[~2023-03-28 18:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-28 18:53 gscfq@t-online.de [this message] 2023-03-28 18:59 ` [Bug c++/109319] " mpolacek at gcc dot gnu.org 2023-03-29 7:06 ` rguenth at gcc dot gnu.org 2023-03-29 11:45 ` [Bug c++/109319] [12/13 Regression] ICE in build_min_non_dep_op_overload, at cp/tree.cc:3793 since r12-5510 jakub at gcc dot gnu.org 2023-03-29 13:38 ` jakub at gcc dot gnu.org 2023-03-30 21:09 ` cvs-commit at gcc dot gnu.org 2023-04-03 13:16 ` [Bug c++/109319] [12 " jakub at gcc dot gnu.org 2023-04-18 7:16 ` cvs-commit at gcc dot gnu.org 2023-04-18 7:20 ` 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-109319-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).