public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102300] [10/11 Regression] Qualified name of same template in class template is rejected Date: Thu, 20 Jan 2022 04:19:41 +0000 [thread overview] Message-ID: <bug-102300-4-nKxpitxBbJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102300-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102300 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10/11/12 Regression] |[10/11 Regression] |Qualified name of same |Qualified name of same |template in class template |template in class template |is rejected |is rejected Known to fail|12.0 | Known to work| |12.0 --- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> --- Fixed for 12 so far.
next prev parent reply other threads:[~2022-01-20 4:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-13 3:07 [Bug c++/102300] New: Qualified name in class template huangqinjin at gmail dot com 2021-09-13 3:18 ` [Bug c++/102300] [11/12 Regression] Qualified name of same template in class template is rejected pinskia at gcc dot gnu.org 2021-09-13 15:51 ` [Bug c++/102300] [10/11/12 " ppalka at gcc dot gnu.org 2022-01-17 13:31 ` rguenth at gcc dot gnu.org 2022-01-18 23:25 ` jason at gcc dot gnu.org 2022-01-20 3:42 ` cvs-commit at gcc dot gnu.org 2022-01-20 4:19 ` jason at gcc dot gnu.org [this message] 2022-04-13 15:06 ` [Bug c++/102300] [10/11 " jakub at gcc dot gnu.org 2022-05-12 22:24 ` cvs-commit at gcc dot gnu.org 2022-05-12 22:25 ` [Bug c++/102300] [11 " jason at gcc dot gnu.org 2022-05-13 12:08 ` cvs-commit at gcc dot gnu.org 2022-05-13 12:11 ` 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-102300-4-nKxpitxBbJ@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).