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++/109300] New: [13 Regression] ICE in cp_finish_decl, at cp/decl.cc:8279
Date: Mon, 27 Mar 2023 18:36:38 +0000	[thread overview]
Message-ID: <bug-109300-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109300
           Summary: [13 Regression] ICE in cp_finish_decl, at
                    cp/decl.cc:8279
           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 20230226 and 20230312 :


$ cat z1.cc
template<typename T>
auto x = [](){ x<int>(); };


$ gcc-13-20230326 -c z1.cc
z1.cc: In instantiation of 'auto x<int>':
z1.cc:2:16:   required from here
z1.cc:2:6: internal compiler error: in cp_finish_decl, at cp/decl.cc:8279
    2 | auto x = [](){ x<int>(); };
      |      ^
0x7a8893 cp_finish_decl(tree_node*, tree_node*, bool, tree_node*, int)
        ../../gcc/cp/decl.cc:8279
0x899b2a instantiate_body
        ../../gcc/cp/pt.cc:26799
0x89aa6f instantiate_decl(tree_node*, bool, bool)
        ../../gcc/cp/pt.cc:27121
0x7b210a maybe_instantiate_decl(tree_node*)
        ../../gcc/cp/decl2.cc:5448
0x7b2c62 mark_used(tree_node*, int)
        ../../gcc/cp/decl2.cc:5747
0x8cc5c3 finish_id_expression_1
        ../../gcc/cp/semantics.cc:4269
0x8cc5c3 finish_id_expression(tree_node*, tree_node*, tree_node*, cp_id_kind*,
bool, bool, bool*, bool, bool, bool, bool, char const**, unsigned int)
        ../../gcc/cp/semantics.cc:4411
0x853ecf cp_parser_primary_expression
        ../../gcc/cp/parser.cc:6149
0x856e76 cp_parser_postfix_expression
        ../../gcc/cp/parser.cc:7777
0x86a60f cp_parser_unary_expression
        ../../gcc/cp/parser.cc:9141
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
0x853967 cp_parser_function_body
        ../../gcc/cp/parser.cc:25335
0x853967 cp_parser_lambda_body
        ../../gcc/cp/parser.cc:11837

             reply	other threads:[~2023-03-27 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 18:36 gscfq@t-online.de [this message]
2023-03-27 19:00 ` [Bug c++/109300] " pinskia at gcc dot gnu.org
2023-03-27 20:46 ` [Bug c++/109300] [13 Regression] ICE in cp_finish_decl, at cp/decl.cc:8279 since r13-6380-gd3d205ab44088616 marxin at gcc dot gnu.org
2023-03-27 20:48 ` mpolacek at gcc dot gnu.org
2023-03-27 23:45 ` ppalka at gcc dot gnu.org
2023-03-28  7:11 ` rguenth at gcc dot gnu.org
2023-04-03 22:50 ` cvs-commit at gcc dot gnu.org
2023-04-03 22:51 ` ppalka 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-109300-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).