Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Michael Eager <eager@eagercon.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] dwarf2_physname
Date: Mon, 31 Aug 2009 23:23:00 -0000	[thread overview]
Message-ID: <4A9C5A66.7060609@redhat.com> (raw)
In-Reply-To: <4A9C54F6.1000909@eagercon.com>

On 08/31/2009 03:55 PM, Michael Eager wrote:

> Does this mean that (eventually) the DW_AT_MIPS_linkage_name attribute
> will not be needed by GDB?

That is exactly what it is intended to do. MIPS_linkage_name is not 
needed in any case I've been able to invent on my 
archer-keiths-expr-cumulative branch, and that branch has MUCH tougher 
C++ tests than FSF gdb does.

> There was a significant amount of discussion about whether this was
> really needed. There were a couple examples where it might provide
> information which was not otherwise available or where it compensated
> for linkers which didn't support weak externs.

This is the first I've heard of this -- thank you for pointing it out. 
My cursory reading of the proposal leaves me torn about whether this 
really changes anything. I've clearly had better results WITHOUT 
DW_AT_MIPS_linkage_name than with it, but I can imagine how having 
DW_AT_linkage_name for certain special situations might be useful.

Perhaps this might just be the beginning of using DW_AT_linkage_name for 
these "special" situations, as opposed to assuming that every object has 
a DW_AT_linkage_name. I don't know. I guess time will tell.

Keith


  reply	other threads:[~2009-08-31 23:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 22:51 Keith Seitz
2009-08-31 23:10 ` Michael Eager
2009-08-31 23:23   ` Keith Seitz [this message]
2009-08-31 23:35     ` Michael Eager
2009-09-01 22:11     ` Daniel Jacobowitz
2009-09-01 22:27       ` Daniel Jacobowitz
2009-09-01 23:18       ` Michael Eager
2009-09-01 23:37         ` Daniel Jacobowitz
2009-09-02  1:12           ` Michael Eager
2009-09-01 23:26       ` Keith Seitz
2009-09-01 23:42         ` Daniel Jacobowitz
2009-09-14 18:39           ` Keith Seitz
2009-09-14 22:48             ` Daniel Jacobowitz
2009-09-14 23:56               ` Keith Seitz
2009-09-15 13:32                 ` Daniel Jacobowitz
2009-09-15 15:53                   ` Keith Seitz
2009-09-15 16:12                     ` Daniel Jacobowitz
2009-09-16 20:27                       ` Keith Seitz
2009-09-18 22:34                         ` Tom Tromey
     [not found]   ` <m37hwjy2tl.fsf@fleche.redhat.com>
2009-09-01  0:06     ` Michael Eager
2009-09-01 21:27 ` Tom Tromey
2009-09-01 22:10   ` Keith Seitz

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=4A9C5A66.7060609@redhat.com \
    --to=keiths@redhat.com \
    --cc=eager@eagercon.com \
    --cc=gdb-patches@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