public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107550] New: incorrect templated lambda mangling Date: Mon, 07 Nov 2022 12:04:02 +0000 [thread overview] Message-ID: <bug-107550-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107550 Bug ID: 107550 Summary: incorrect templated lambda mangling Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nathan at gcc dot gnu.org Target Milestone: --- I got something wrong in template lambda manglings, discovered when working on the demangler (uncommitted). Confirmed with clang. We get the wrong mangling, somehow losing the template-head of the lambda. template<typename T> class X; inline void f () { auto l3 = []<typename T>(X<T> *, X<int> *) {}; l3 ((X<char> *)nullptr, nullptr); // _ZZ1fvENKUlTyP1XIT_EPS_IiEE _clIcEEDaS2_S4_ Correct // _ZZ1fvENKUl P1XIT_EPS_IiEE0_clIcEEDaS2_S4_ Wrong } void a () { f (); }
next reply other threads:[~2022-11-07 12:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-07 12:04 nathan at gcc dot gnu.org [this message] 2022-11-07 18:25 ` [Bug c++/107550] " nathan at gcc dot gnu.org 2022-11-28 22:14 ` pinskia 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-107550-4@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).