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++/108437] New: [13 Regression] ICE in build_min_non_dep_op_overload, at cp/tree.cc:3710
Date: Tue, 17 Jan 2023 17:52:31 +0000	[thread overview]
Message-ID: <bug-108437-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108437

            Bug ID: 108437
           Summary: [13 Regression] ICE in build_min_non_dep_op_overload,
                    at cp/tree.cc:3710
           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 :


$ 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]++;
  return 0;
}


$ g++-13-20230115 -c z1.cc -std=c++23
z1.cc: In function 'int f()':
z1.cc:8:6: internal compiler error: in build_min_non_dep_op_overload, at
cp/tree.cc:3710
    8 |   s[0]++;
      |      ^
0xb397f7 build_min_non_dep_op_overload(tree_code, tree_node*, tree_node*, ...)
        ../../gcc/cp/tree.cc:3710
0x92b620 grok_array_decl(unsigned int, tree_node*, tree_node*, vec<tree_node*,
va_gc, vl_embed>**, int)
        ../../gcc/cp/decl2.cc:577
0xa17963 cp_parser_postfix_open_square_expression
        ../../gcc/cp/parser.cc:8177
0xa2b2de cp_parser_postfix_expression
        ../../gcc/cp/parser.cc:7768
0xa44ddf cp_parser_unary_expression
        ../../gcc/cp/parser.cc:9095
0xa106ef cp_parser_cast_expression
        ../../gcc/cp/parser.cc:9999
0xa1101f cp_parser_binary_expression
        ../../gcc/cp/parser.cc:10101
0xa11da4 cp_parser_assignment_expression
        ../../gcc/cp/parser.cc:10444
0xa14362 cp_parser_expression
        ../../gcc/cp/parser.cc:10614
0xa18577 cp_parser_expression_statement
        ../../gcc/cp/parser.cc:12758
0xa26ae1 cp_parser_statement
        ../../gcc/cp/parser.cc:12538
0xa27de4 cp_parser_statement_seq_opt
        ../../gcc/cp/parser.cc:12909
0xa27ec7 cp_parser_compound_statement
        ../../gcc/cp/parser.cc:12861
0xa51d90 cp_parser_function_body
        ../../gcc/cp/parser.cc:25280
0xa51d90 cp_parser_ctor_initializer_opt_and_function_body
        ../../gcc/cp/parser.cc:25331
0xa5240a cp_parser_function_definition_after_declarator
        ../../gcc/cp/parser.cc:31953
0xa5393c cp_parser_function_definition_from_specifiers_and_declarator
        ../../gcc/cp/parser.cc:31870
0xa5393c cp_parser_init_declarator
        ../../gcc/cp/parser.cc:22734
0xa5713f cp_parser_single_declaration
        ../../gcc/cp/parser.cc:32470
0xa572a6 cp_parser_template_declaration_after_parameters
        ../../gcc/cp/parser.cc:32023

             reply	other threads:[~2023-01-17 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 17:52 gscfq@t-online.de [this message]
2023-01-17 21:02 ` [Bug c++/108437] " mpolacek at gcc dot gnu.org
2023-01-18  9:00 ` rguenth at gcc dot gnu.org
2023-01-18 16:23 ` jakub at gcc dot gnu.org
2023-01-19 22:31 ` cvs-commit at gcc dot gnu.org
2023-01-19 22:33 ` 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-108437-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).