public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dblaikie at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107741] New: Missed member variable name in mangling of externally visible lambdas used in inline initialization of static members Date: Fri, 18 Nov 2022 01:05:17 +0000 [thread overview] Message-ID: <bug-107741-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107741 Bug ID: 107741 Summary: Missed member variable name in mangling of externally visible lambdas used in inline initialization of static members Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dblaikie at gmail dot com Target Milestone: --- https://godbolt.org/z/7514cTh5o ``` struct A { static constexpr auto x = [] { return 1; }; }; template <typename> struct B { static constexpr auto x = [] { return 1; }; }; template <typename T> struct C { static int x; }; void side_effect(); template <typename T> int C<T>::x = (side_effect(), [] { return 1; }()); template int C<int>::x; void f() { A::x(); B<int>::x(); } ``` GCC produces these manglings: ``` A::{lambda()#1}::operator()() const _ZNK1AUlvE_clEv B<int>::{lambda()#3}::operator()() const _ZNK1BIiEUlvE1_clEv C<int>::x::{lambda()#1}::operator()() const _ZNK1CIiE1xMUlvE_clEv ``` I believe in the first two cases, the member variable scope ("::x") is missing. Oh, and it looks like the lambda numbering is off - B's lambda is 1 within its scope (either the type or the member) - so I guess that needs to be fixed too/scoping the numbering to within the member along with the mangling having that scoping.
next reply other threads:[~2022-11-18 1:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-18 1:05 dblaikie at gmail dot com [this message] 2022-11-18 1:08 ` [Bug c++/107741] " dblaikie at gmail dot com 2023-03-07 6:32 ` dblaikie at gmail dot com
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-107741-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).