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++/104235] [12 Regression] ICE: in cp_parser_template_id, at cp/parser.cc Date: Wed, 26 Jan 2022 00:26:27 +0000 [thread overview] Message-ID: <bug-104235-4-DGkTCONp19@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104235-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104235 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Keywords|needs-bisection | CC| |mpolacek at gcc dot gnu.org Last reconfirmed| |2022-01-26 Priority|P3 |P1 Ever confirmed|0 |1 --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- commit 30f2c22def7392119f1ffaca30ef998b3b43f336 Author: Jason Merrill <jason@redhat.com> Date: Tue Jan 18 18:28:22 2022 -0500 c++: template-id with current inst qualifier [PR102300] The patch for PR41723 properly changed one place to look into the current instantiation; now we need to fix this place as well. PR c++/102300 gcc/cp/ChangeLog: * parser.cc (cp_parser_template_name): Use dependent_scope_p. gcc/testsuite/ChangeLog: * g++.dg/parse/no-typename1.C: Remove expected error. * g++.dg/template/nested7.C: New test.
next prev parent reply other threads:[~2022-01-26 0:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-26 0:20 [Bug c++/104235] New: " glisse at gcc dot gnu.org 2022-01-26 0:22 ` [Bug c++/104235] " pinskia at gcc dot gnu.org 2022-01-26 0:26 ` mpolacek at gcc dot gnu.org [this message] 2022-01-26 0:59 ` mpolacek at gcc dot gnu.org 2022-01-26 15:30 ` jason at gcc dot gnu.org 2022-01-26 16:39 ` cvs-commit at gcc dot gnu.org 2022-01-26 16:40 ` jason 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-104235-4-DGkTCONp19@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).