public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/91618] template-id required to friend a function template, even for a qualified-id Date: Mon, 13 Dec 2021 16:06:20 +0000 [thread overview] Message-ID: <bug-91618-4-HAoyYQ3CqP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91618-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91618 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Even though PR 100339 is newer, it has more details on the issue and even references the revision which introduced the regressions so closing this issue as a dup of bug 100339. *** This bug has been marked as a duplicate of bug 100339 ***
next prev parent reply other threads:[~2021-12-13 16:06 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91618-4@http.gcc.gnu.org/bugzilla/> 2020-08-29 15:06 ` language.lawyer at gmail dot com 2020-11-04 15:51 ` redi at gcc dot gnu.org 2020-11-04 15:51 ` redi at gcc dot gnu.org 2021-12-13 16:06 ` pinskia at gcc dot gnu.org [this message] 2021-12-13 16:07 ` pinskia at gcc dot gnu.org 2021-12-13 16:09 ` [Bug c++/91618] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-17 9:00 ` rguenth at gcc dot gnu.org 2022-04-07 15:59 ` jason at gcc dot gnu.org 2022-04-07 20:11 ` jason at gcc dot gnu.org 2022-04-09 1:51 ` cvs-commit at gcc dot gnu.org 2022-04-29 21:25 ` [Bug c++/91618] [9/10/11 " cvs-commit at gcc dot gnu.org 2022-05-13 15:29 ` jason at gcc dot gnu.org 2023-05-03 19:25 ` cvs-commit 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-91618-4-HAoyYQ3CqP@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).