public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "robert at ocallahan dot 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: Wed, 29 Apr 2020 11:29:45 +0000	[thread overview]
Message-ID: <bug-94845-4-3e6brypR4y@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

--- Comment #1 from robert at ocallahan dot org <robert at ocallahan dot org> ---
One case where this causes problems is implementing a debugger where you want
to be able to evaluate expressions containing type names. Type names containing
template type parameters that are base types need to be normalized to match the
type names in the debuginfo. g++ requires us to normalize those type names in a
way that's different from the C++ demangler and from clang++.

  reply	other threads:[~2020-04-29 11:29 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 ` robert at ocallahan dot org [this message]
2020-04-29 11:50 ` [Bug c++/94845] " 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
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-3e6brypR4y@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).