public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/43377] lto decreases C++ stacktrace readability (debuginfo pubnames).
Date: Fri, 23 Apr 2010 13:23:00 -0000 [thread overview]
Message-ID: <20100423132335.21446.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43377-7667@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from rguenth at gcc dot gnu dot org 2010-04-23 13:23 -------
(In reply to comment #2)
> Because we drop DECL_CONTEXT.
Rather because lang_hooks.dwarf_name returns what
lang_hooks.decl_printable_name
returns which in turn returns DECL_NAME.
We can either save what the langhook produces in DECL_NAME during fld or
for example use the assembler name (which is mangled). Of course the
langhook has a variant to request a name with or without the scope ...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43377
next prev parent reply other threads:[~2010-04-23 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 11:48 [Bug lto/43377] New: lto decreases " pluto at agmk dot net
2010-03-15 11:50 ` [Bug lto/43377] " pluto at agmk dot net
2010-03-15 12:51 ` [Bug lto/43377] lto decreases C++ " rguenth at gcc dot gnu dot org
2010-04-23 13:23 ` rguenth at gcc dot gnu dot org [this message]
[not found] <bug-43377-4@http.gcc.gnu.org/bugzilla/>
2012-03-15 21:23 ` pluto at agmk dot net
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=20100423132335.21446.qmail@sourceware.org \
--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).