public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "swagiaal at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/37982] Extraneous DW_TAG_variable tag
Date: Mon, 01 Dec 2008 16:13:00 -0000	[thread overview]
Message-ID: <20081201161223.7906.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37982-11288@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from swagiaal at redhat dot com  2008-12-01 16:12 -------
> DW_AT_MIPS_linkage_name should be removed from GCC only after the DW_AT_name
> scoping/qualification will get fully fixed.  GDB currently already contains the
> DW_AT_MIPS_linkage_name reader and there is probably no need to disable it
> (except for testing purposes).
> 

Agreed. My patch fixes test cases where DW_AT_MIPS_linkage_name was not
generated by gcc, but the patch should be smarter about falling back on
DW_AT_MIPS_linkage_name when the correct canonical name cannot be constructed.

> On GDB CVS HEAD for gdb.cp/m-static.exp a command `print gnu_obj_4::elsewhere'
> works for me as it can find (presumably) the corrent .symtab mangled symbol.
> 
> Sure it would be good to get DW_AT_name fixed in GCC.
> 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37982


  parent reply	other threads:[~2008-12-01 16:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 19:05 [Bug debug/37982] New: Extranious " swagiaal at redhat dot com
2008-10-31 19:07 ` [Bug debug/37982] " swagiaal at redhat dot com
2008-10-31 19:08 ` swagiaal at redhat dot com
2008-10-31 19:08 ` swagiaal at redhat dot com
2008-11-01 11:05 ` [Bug debug/37982] Extraneous " dodji at gcc dot gnu dot org
2008-11-28  1:38 ` jan dot kratochvil at redhat dot com
2008-11-28 16:34 ` swagiaal at redhat dot com
2008-11-29  0:25 ` jan dot kratochvil at redhat dot com
2008-12-01 16:13 ` swagiaal at redhat dot com [this message]
2010-03-17 21:15 ` dodji at gcc dot gnu dot org
2010-03-18 12:53 ` dodji at gcc dot gnu dot org
2010-03-18 12:53 ` dodji at gcc dot gnu dot 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=20081201161223.7906.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).