From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Another Fortran problem...
Date: Fri, 26 Oct 2007 12:03:00 -0000 [thread overview]
Message-ID: <20071026120351.GC26327@caradoc.them.org> (raw)
In-Reply-To: <19c433eb0710260339w341f3437u4797445de7bc36d@mail.gmail.com>
On Fri, Oct 26, 2007 at 11:39:11AM +0100, Fran?ois-Xavier Coudert wrote:
> Is "DW_AT_MIPS_linkage_name: foo_" the reason for this difference?
Yes.
> Should DW_AT_MIPS_linkage_name actually be emitted or is this wrong?
I'm not sure. I was just looking at this problem; I have some
in-progress patches that remove GDB's use of DW_AT_MIPS_linkage_name,
and I was very surprised when they fixed a recent gnats PR about
a similar Fortran problem.
"foo_" is really the linkage name, so if gfortran wants to emit
DW_AT_MIPS_linkage_name then that's the value it should have. But
GDB doesn't have a demangler for Fortran mangled names so
it ends up stuck with the mangled name.
What sort of mangling does gfortran do? Should we be able to demangle
it? Or just ignore linkage names for Fortran?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-26 12:03 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 [this message]
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
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=20071026120351.GC26327@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