From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5190 invoked by alias); 13 Jun 2003 01:01:38 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 5157 invoked from network); 13 Jun 2003 01:01:37 -0000 Received: from unknown (HELO smtp6.Stanford.EDU) (171.67.16.33) by sources.redhat.com with SMTP; 13 Jun 2003 01:01:37 -0000 Received: (from root@localhost) by smtp6.Stanford.EDU (8.12.9/8.12.9) id h5D11bJm016236 for gdb-patches@sources.redhat.com; Thu, 12 Jun 2003 18:01:37 -0700 (PDT) Received: from jackfruit.Stanford.EDU (jackfruit.Stanford.EDU [171.64.38.136]) by smtp6.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h5D11S5U016197; Thu, 12 Jun 2003 18:01:33 -0700 (PDT) Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h5D11SO14445; Thu, 12 Jun 2003 18:01:28 -0700 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa] always use demangled name to set scope References: <20030612231727.GA19870@nevyn.them.org> From: David Carlton Date: Fri, 13 Jun 2003 01:01:00 -0000 In-Reply-To: <20030612231727.GA19870@nevyn.them.org> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-06/txt/msg00446.txt.bz2 On Thu, 12 Jun 2003 19:17:27 -0400, Daniel Jacobowitz said: > On Thu, Jun 12, 2003 at 03:26:34PM -0700, David Carlton wrote: >> OK to commit? > Yes. Thanks, committed. > By 6.1 I want to rip out all uses of the demangled name along the > DWARF-2 code path though. If I can find the time... We'll see. I do think that the nested type deduction machinery is both useful and impossible to do without demangled names. And there are fun bits like how gnuv3_rtti_type looks at the demangled name of the vtable. If it were possible to get rid of that, I would be a happy person indeed, since its existence is probably going to force me to change the demangler's output somewhat. (On the other hand, that call is also a useful canary in the coal mine, too, because of the RTTI warning that comes out of it.) But I really am getting a pretty good feel for how to use the hierarchical info in DWARF to help us here. And people at Kealia have given me some very useful bug reports along those lines: this would be impossible to get at all right without a large C++ code base to trigger all sorts of random GCC idiosyncracies. David Carlton carlton@math.stanford.edu