public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94845] DWARF function name doesn't match demangled name in base type template parameters Date: Thu, 22 Apr 2021 19:06:28 +0000 [thread overview] Message-ID: <bug-94845-4-FdONivJSUW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94845-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845 Tom Tromey <tromey at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at gcc dot gnu.org --- Comment #6 from Tom Tromey <tromey at gcc dot gnu.org> --- gdb does this canonicalization precisely because the form in the DWARF cannot be relied upon. It would be great to remove this, because it is expensive. One idea for a migration route would be for g++ to promise to emit the same form that the demangler emits; then add an attribute to the comp-unit DIE saying that the names have been canonicalized. (Or, I suppose gdb could use producer sniffing; but I'd rather avoid that as much as possible.)
next prev parent reply other threads:[~2021-04-22 19:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-29 11:03 [Bug c++/94845] New: " robert at ocallahan dot org 2020-04-29 11:29 ` [Bug c++/94845] " robert at ocallahan dot org 2020-04-29 11:50 ` pinskia at gcc dot gnu.org 2020-04-29 11:52 ` pinskia at gcc dot gnu.org 2020-04-29 12:00 ` pinskia at gcc dot gnu.org 2020-04-29 12:19 ` robert at ocallahan dot org 2021-04-22 19:06 ` tromey at gcc dot gnu.org [this message] 2021-04-22 22:49 ` robert at ocallahan dot org 2021-04-23 1:38 ` tromey at gcc dot gnu.org 2021-04-23 2:27 ` robert at ocallahan dot org 2022-10-21 17:48 ` tromey 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-94845-4-FdONivJSUW@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).