public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110006] [11/12 Regression] friend function template with constraint doesn't match existing declaration Date: Mon, 15 Apr 2024 15:33:45 +0000 [thread overview] Message-ID: <bug-110006-4-xjRlBqQpiD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110006-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110006 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[11/12/13 Regression] |[11/12 Regression] friend |friend function template |function template with |with constraint doesn't |constraint doesn't match |match existing declaration |existing declaration --- Comment #6 from Patrick Palka <ppalka at gcc dot gnu.org> --- Now also backported for GCC 13.3 as r13-8608-g38c2679ff9330d and r13-8609-g265f207a46bc38.
prev parent reply other threads:[~2024-04-15 15:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-27 17:33 [Bug c++/110006] New: friend function template with NTTP and " services+gccbugs at vasama dot org 2023-06-16 20:44 ` [Bug c++/110006] friend function template with " waffl3x at protonmail dot com 2023-07-10 6:20 ` [Bug c++/110006] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-07-12 13:39 ` ppalka at gcc dot gnu.org 2024-01-12 13:56 ` rguenth at gcc dot gnu.org 2024-02-03 0:07 ` cvs-commit at gcc dot gnu.org 2024-02-03 0:11 ` [Bug c++/110006] [11/12/13 " ppalka at gcc dot gnu.org 2024-02-03 0:13 ` ppalka at gcc dot gnu.org 2024-04-15 15:33 ` ppalka 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-110006-4-xjRlBqQpiD@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).