From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5588 invoked by alias); 10 Jul 2003 14:54:59 -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 5563 invoked from network); 10 Jul 2003 14:54:59 -0000 Received: from unknown (HELO sccrmhc12.comcast.net) (204.127.202.56) by sources.redhat.com with SMTP; 10 Jul 2003 14:54:59 -0000 Received: from lucon.org ([12.234.88.5]) by comcast.net (sccrmhc12) with ESMTP id <2003071014545801200dudd6e>; Thu, 10 Jul 2003 14:54:58 +0000 Received: by lucon.org (Postfix, from userid 1000) id B5A702C510; Thu, 10 Jul 2003 14:54:57 +0000 (UTC) Date: Thu, 10 Jul 2003 14:54:00 -0000 From: "H. J. Lu" To: binutils@sources.redhat.com, gdb@sources.redhat.com Subject: Re: FYI: A new C++ demangler Message-ID: <20030710145457.GA26001@lucon.org> References: <20030710143557.GA25588@lucon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SW-Source: 2003-07/txt/msg00124.txt.bz2 On Thu, Jul 10, 2003 at 07:39:53AM -0700, Ian Lance Taylor wrote: > "H. J. Lu" writes: > > > I will put a new C++ demangler in Linux binutils, which should fix all > > known bugs in the old demangler. It is written in C++. It will be > > enabled only if there is a working C++ compiler. Otherwise, the old > > demangler will be used. > > Are you coordinating with the g++ developers? > I guess you didn't follow the gcc mailing list very much. The short story is I can't get it into libiberty. I tried several months without much success. Libiberty doesn't want a C++ demangler written in C++ and I have no interest in fixing the old one. BTW, the new C++ demangler is 100% compatible with the old one. I have been using it for months. H.J.