From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Another Fortran problem...
Date: Fri, 26 Oct 2007 14:06:00 -0000 [thread overview]
Message-ID: <20071026140556.GA23513@caradoc.them.org> (raw)
In-Reply-To: <19c433eb0710260658y750befb3k290ccddbcf6d0ad1@mail.gmail.com>
On Fri, Oct 26, 2007 at 02:58:35PM +0100, Fran?ois-Xavier Coudert wrote:
> > Somewhat impractical. I think we would be best off ignoring linkage
> > names for Fortran, or else GCC not emitting them... I don't know
> > which. Won't they generally match the names in the ELF symbol table?
>
> Yes, they probably will. Don't they serve any other useful purpose?
> (not emitting them in GCC fixes the problem)
I'm not sure. In C++ we use them to extract namespace and class
hierarchy information, which was only represented in DWARF relatively
recently (circa 3.3). They should be unnecessary now in most cases
and other compilers do not admit them.
I can see how they could be useful for non-defining declarations, in
case the definition was in an object without debugging information.
Let's give it a day or two in case anyone else has comments, but I
don't think DW_AT_MIPS_linkage_name has any benefit for Fortran
support. In that case, we can change GCC HEAD not to emit them and
GDB not to use them.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-26 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 10:39 François-Xavier Coudert
2007-10-26 12:03 ` Daniel Jacobowitz
2007-10-26 13:05 ` François-Xavier Coudert
2007-10-26 13:14 ` Daniel Jacobowitz
2007-10-26 13:58 ` François-Xavier Coudert
2007-10-26 14:06 ` Daniel Jacobowitz [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=20071026140556.GA23513@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.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