public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110687] problem with class template Date: Mon, 17 Jul 2023 09:13:35 +0000 [thread overview] Message-ID: <bug-110687-4-rDJPCQF8G7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110687-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110687 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Fixed for 12.1 and 11.4 by: 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. Probably a dup of PR 41723.
prev parent reply other threads:[~2023-07-17 9:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-16 15:25 [Bug c++/110687] New: " irip at qq dot com 2023-07-17 7:32 ` [Bug c++/110687] " rguenth at gcc dot gnu.org 2023-07-17 9:13 ` redi at gcc dot gnu.org [this message]
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-110687-4-rDJPCQF8G7@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).