From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22427 invoked by alias); 31 Aug 2009 22:56:01 -0000 Received: (qmail 22418 invoked by uid 22791); 31 Aug 2009 22:56:00 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_20 X-Spam-Check-By: sourceware.org Received: from shell4.BAYAREA.NET (HELO shell4.bayarea.net) (209.128.82.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 31 Aug 2009 22:55:54 +0000 Received: (qmail 14151 invoked from network); 31 Aug 2009 15:55:52 -0700 Received: from 209-128-106-254.bayarea.net (HELO redwood.eagercon.com) (209.128.106.254) by shell4.bayarea.net with SMTP; 31 Aug 2009 15:55:51 -0700 Message-ID: <4A9C54F6.1000909@eagercon.com> Date: Mon, 31 Aug 2009 23:10:00 -0000 From: Michael Eager User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: Keith Seitz CC: gdb-patches@sourceware.org Subject: Re: [RFA] dwarf2_physname References: <4A9C358E.2050904@redhat.com> In-Reply-To: <4A9C358E.2050904@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-08/txt/msg00597.txt.bz2 Keith Seitz wrote: > > To start, I would like to submit a patch which is the beginnings of > removing GDB's use of the DWARF2 quasi-attribute > DW_AT_MIPS_linkage_name. Instead of using this attribute, GDB will start > generating physical names itself. Does this mean that (eventually) the DW_AT_MIPS_linkage_name attribute will not be needed by GDB? Coincidentally, the Dwarf Committee just approved adding DW_AT_linkage_name to DWARF Version 4. The semantics are substantially the same as DW_AT_MIPS_linkage_name. (http://www.dwarfstd.org/ShowIssue.php?issue=090715.1&type=closed3) The semantics are substantially the same as DW_AT_MIPS_linkage_name. 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. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077