From: Jason Merrill <jason@redhat.com>
To: gcc@gcc.gnu.org
Cc: Daniel Berlin <dan@cgsoftware.com>
Subject: Re: DWARF-2 and constructors/destructors
Date: Thu, 06 Dec 2001 10:39:00 -0000 [thread overview]
Message-ID: <wvllmggxlgq.fsf@prospero.cambridge.redhat.com> (raw)
In-Reply-To: <20011205225246.A10961@nevyn.them.org> (Daniel Jacobowitz's message of "Wed, 5 Dec 2001 22:52:46 -0500")
>>>>> "Daniel" == Daniel Jacobowitz <dmj+@andrew.cmu.edu> writes:
> Suppose you want to call a (non-virtual) method in C++, from something
> with Dwarf-2 info. The only way to get the mangled name from the debug
> info is DW_AT_MIPS_linkage_name.
As Dan Berlin points out, The mangled name is already in the symbol table,
if there's actually a definition of the method. Why does it need to be in
the debug info as well? To call a non-virtual function, we're only
interested in its address. The debug information doesn't enter into it.
This applies to all functions, of course, not just ctors/dtors. The
DW_AT_MIPS_linkage_name stuff was a hack to make dwarf2 work with the
existing stabs-oriented code with minimal effort; it would save a lot of
space if we could get rid of it.
Jason
prev parent reply other threads:[~2001-12-06 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 19:53 Daniel Jacobowitz
2001-12-05 20:01 ` Daniel Jacobowitz
2001-12-05 20:25 ` Daniel Berlin
2001-12-06 10:39 ` Jason Merrill [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=wvllmggxlgq.fsf@prospero.cambridge.redhat.com \
--to=jason@redhat.com \
--cc=dan@cgsoftware.com \
--cc=gcc@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).