public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/49537] New: cross-check DW_AT_name vs. demangling of linkage names
Date: Sun, 26 Jun 2011 22:45:00 -0000 [thread overview]
Message-ID: <bug-49537-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49537
Summary: cross-check DW_AT_name vs. demangling of linkage names
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: debug
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jan.kratochvil@redhat.com
CC: dodji@gcc.gnu.org
PR debug/49408 shows DW_AT_name "K<&S::m>" vs. demangled
DW_AT_MIPS_linkage_name prefix "K<&(S::m(int))>". This was due to a bug in
libiberty/cp-demangle.c.
http://gcc.gnu.org/ml/gcc/2011-06/msg00308.html
On Wed, Jun 22, 2011 at 10:42 AM, Jason Merrill <jason at redhat.com> wrote:
> Well, the basic issue is that the "linkage name" is produced
> by libiberty/cp-demangle.c and the DW_AT_name is produced by gcc/cp/error.c,
> and they don't always agree on the same pretty-printed representation
> of a C++ expression.
Therefore I believe there could be compile time sanity cross-check with ICE in
such cases, maybe more such bugs exist there already.
next reply other threads:[~2011-06-26 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 22:45 jan.kratochvil at redhat dot com [this message]
2011-06-27 17:14 ` [Bug debug/49537] " jason 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-49537-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: 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).