From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32033 invoked by alias); 30 Nov 2003 02:57:27 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 32026 invoked from network); 30 Nov 2003 02:57:26 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 30 Nov 2003 02:57:26 -0000 Received: by zenia.home (Postfix, from userid 5433) id 8A94520766; Sat, 29 Nov 2003 21:56:28 -0500 (EST) To: Daniel Jacobowitz Cc: Ian Lance Taylor , gdb Subject: Re: C++/Java regressions References: <20031126153234.GA10644@nevyn.them.org> <20031126211228.GA13423@nevyn.them.org> From: Jim Blandy Date: Sun, 30 Nov 2003 02:57:00 -0000 In-Reply-To: <20031126211228.GA13423@nevyn.them.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-11/txt/msg00297.txt.bz2 Daniel Jacobowitz writes: > > If it helps, that's more or less what my libiberty C++ demangler does. > > It first translate the name into a simple tree structure, and then > > walks the tree translating it into a string. I could expose the tree, > > although it would have to be documented a bit better. > > Oh, so it's already two-pass? If we could work out an API for the > tree, then GDB could build and supply trees to get a canonical form > back from the demangler. That has the added bonus of not needing to > post-process the demangler output (if we know that we've got a GNU v3 > name and thus this demangler was used, of course - v2 would still need > to be parsed). That sounds like an ideal solution. I've been wanting something like this for a long time, too.