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++/105229] New: [11/12 Regression] ICE in lookup_template_class_1, at cp/pt.cc:10111
Date: Mon, 11 Apr 2022 16:55:40 +0000	[thread overview]
Message-ID: <bug-105229-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105229
           Summary: [11/12 Regression] ICE in lookup_template_class_1, at
                    cp/pt.cc:10111
           Product: gcc
           Version: 12.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 20200503 and 20200510 :


$ cat z1.cc
template <typename> void bar ()
{
  [] <int> {}.operator () <> ();
}
void foo ()
{
  bar<int> ();
}


$ g++-12-20220410 -c z1.cc
z1.cc: In instantiation of 'void bar() [with <template-parameter-1-1> = int]':
z1.cc:7:12:   required from here
z1.cc:3:28: internal compiler error: in lookup_template_class_1, at
cp/pt.cc:10111
    3 |   [] <int> {}.operator () <> ();
      |   ~~~~~~~~~~~~~~~~~~~~~~~~~^
0x990981 lookup_template_class_1
        ../../gcc/cp/pt.cc:10111
0x990981 lookup_template_class(tree_node*, tree_node*, tree_node*, tree_node*,
int, int)
        ../../gcc/cp/pt.cc:10350
0x990cb2 tsubst_aggr_type
        ../../gcc/cp/pt.cc:13738
0x97a962 tsubst(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/cp/pt.cc:15649
0x9a717b tsubst_baselink
        ../../gcc/cp/pt.cc:16453
0x976d2b tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc/cp/pt.cc:21028
0x975385 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc/cp/pt.cc:20658
0x99b274 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc/cp/pt.cc:19473
0x99918d tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc/cp/pt.cc:18486
0x999b9f tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc/cp/pt.cc:18458
0x99b233 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc/cp/pt.cc:18815
0x97f679 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc/cp/pt.cc:18444
0x97f679 instantiate_body
        ../../gcc/cp/pt.cc:26393
0x980da7 instantiate_decl(tree_node*, bool, bool)
        ../../gcc/cp/pt.cc:26685
0x9c780b instantiate_pending_templates(int)
        ../../gcc/cp/pt.cc:26764
0x8281e6 c_parse_final_cleanups()
        ../../gcc/cp/decl2.cc:5113

             reply	other threads:[~2022-04-11 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 16:55 gscfq@t-online.de [this message]
2022-04-11 17:10 ` [Bug c++/105229] " mpolacek at gcc dot gnu.org
2022-04-12  7:43 ` rguenth at gcc dot gnu.org
2022-04-21  7:51 ` rguenth at gcc dot gnu.org
2023-03-23 19:00 ` [Bug c++/105229] [11/12/13 " pinskia at gcc dot gnu.org
2023-05-29 10:06 ` [Bug c++/105229] [11/12/13/14 " jakub at gcc dot gnu.org
2024-04-30 14:50 ` [Bug c++/105229] [11/12/13/14/15 " simartin at gcc dot gnu.org
2024-05-06 18:59 ` simartin 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-105229-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).