public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105229] [11/12 Regression] ICE in lookup_template_class_1, at cp/pt.cc:10111 Date: Mon, 11 Apr 2022 17:10:32 +0000 [thread overview] Message-ID: <bug-105229-4-lJUkvR4311@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105229-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105229 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |mpolacek at gcc dot gnu.org Status|UNCONFIRMED |NEW Last reconfirmed| |2022-04-11 Target Milestone|--- |11.3 --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Confirmed. Started with r11-86-gef3479afc5ab41 commit ef3479afc5ab415f00a53fc6f6a990df7f6a0747 Author: Marek Polacek <polacek@redhat.com> Date: Tue Apr 28 22:30:44 2020 -0400 c++: Member template function lookup failure [PR94799] which changed $ ./cc1plus.r11-85 -quiet ~/105229.C -std=c++2a /home/mpolacek/105229.C: In function ‘void bar()’: /home/mpolacek/105229.C:3:12: error: expected ‘(’ before ‘{’ token 3 | [] <int> {}.operator () <> (); | ^ | ( /home/mpolacek/105229.C:3:28: error: expected primary-expression before ‘>’ token 3 | [] <int> {}.operator () <> (); | ^ /home/mpolacek/105229.C:3:31: error: expected primary-expression before ‘)’ token 3 | [] <int> {}.operator () <> (); | ^ to $ ./cc1plus.r11-86 -quiet ~/105229.C -std=c++2a /home/mpolacek/105229.C: In function ‘void bar()’: /home/mpolacek/105229.C:3:12: error: expected ‘(’ before ‘{’ token 3 | [] <int> {}.operator () <> (); | ^ | ( /home/mpolacek/105229.C: In instantiation of ‘void bar() [with <template-parameter-1-1> = int]’: /home/mpolacek/105229.C:7:13: required from here /home/mpolacek/105229.C:3:28: internal compiler error: in lookup_template_class_1, at cp/pt.c:9891 3 | [] <int> {}.operator () <> (); | ~~~~~~~~~~~~~~~~~~~~~~~~~^ unrecognized DWARF version in .debug_info at 6 0xbc18c9 lookup_template_class_1 ../../gcc/cp/pt.c:9891 0xbc3176 lookup_template_class(tree_node*, tree_node*, tree_node*, tree_node*, int, int) ../../gcc/cp/pt.c:10114 0xbd10d0 tsubst_aggr_type ../../gcc/cp/pt.c:13382 0xbdd578 tsubst(tree_node*, tree_node*, int, tree_node*) ../../gcc/cp/pt.c:15169 0xbe0fe1 tsubst_baselink ../../gcc/cp/pt.c:16001 0xbf8c92 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool, bool) ../../gcc/cp/pt.c:20188 0xbf638e tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool, bool) ../../gcc/cp/pt.c:19730 0xbf1cd2 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool) ../../gcc/cp/pt.c:18753 0xbea656 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool) ../../gcc/cp/pt.c:17865 0xbea3e8 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool) ../../gcc/cp/pt.c:17835 0xbed092 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool) ../../gcc/cp/pt.c:18154 0xc11905 instantiate_decl(tree_node*, bool, bool) ../../gcc/cp/pt.c:25714 0xc122c4 instantiate_pending_templates(int) ../../gcc/cp/pt.c:25830
next prev parent reply other threads:[~2022-04-11 17:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-11 16:55 [Bug c++/105229] New: " gscfq@t-online.de 2022-04-11 17:10 ` mpolacek at gcc dot gnu.org [this message] 2022-04-12 7:43 ` [Bug c++/105229] " 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-lJUkvR4311@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).