public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109422] wrong depth used for template parameter mangling for lambdas in function signatures Date: Tue, 10 Oct 2023 21:23:27 +0000 [thread overview] Message-ID: <bug-109422-4-TldzVg3YpA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109422-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109422 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:bd5719bd7f7cb23e5ed96a1f1a28efbb3dec4a31 commit r14-4544-gbd5719bd7f7cb23e5ed96a1f1a28efbb3dec4a31 Author: Jason Merrill <jason@redhat.com> Date: Fri Oct 6 11:41:20 2023 -0400 c++: mangle multiple levels of template parms [PR109422] This becomes be more important with concepts, but can also be seen with generic lambdas. PR c++/109422 gcc/cp/ChangeLog: * mangle.cc (write_template_param): Also mangle level. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/lambda-generic-mangle1.C: New test. * g++.dg/cpp2a/lambda-generic-mangle1a.C: New test.
next prev parent reply other threads:[~2023-10-10 21:23 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-05 17:36 [Bug c++/109422] New: " richard-gccbugzilla at metafoo dot co.uk 2023-04-05 17:39 ` [Bug c++/109422] " richard-gccbugzilla at metafoo dot co.uk 2023-10-10 21:23 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-17 2:42 ` 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-109422-4-TldzVg3YpA@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).