public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109020] Lambdas have different DWARF signature than the function they are in
Date: Mon, 06 Mar 2023 08:34:56 +0000 [thread overview]
Message-ID: <bug-109020-4-cJIpiFcryF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109020-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109020
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |MOVED
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Nothing in DWARF can change the scope name of a child DIE and I don't see
any mangled symbol name output either so it must be gdb being funky possibly
using the symbol demangling in one and the dwarf name in the other completion.
_ZZL2ffmENKUlvE_clEv
demangles as
ff(unsigned long)::{lambda()#1}::operator()() const
no typedefs in manglings, obviously. Please file on the sourceware side.
prev parent reply other threads:[~2023-03-06 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 10:09 [Bug c++/109020] New: " jengelh at inai dot de
2023-03-06 8:34 ` rguenth 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-109020-4-cJIpiFcryF@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: link
Be 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).