From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27117 invoked by alias); 13 Sep 2006 09:01:19 -0000 Received: (qmail 27090 invoked by uid 48); 13 Sep 2006 09:01:18 -0000 Date: Wed, 13 Sep 2006 09:01:00 -0000 Message-ID: <20060913090118.27089.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug java/29044] Libiberty demangler can not handle new Java mangling. In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "aph at gcc dot gnu dot org" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2006-q3/txt/msg00314.txt.bz2 List-Id: ------- Comment #6 from aph at gcc dot gnu dot org 2006-09-13 09:01 ------- I don't understand why this bug has been reported. Are you using an up-to-date libiberty to do the demangling? When I try c++filt --format java, I get Hello.main(java.lang.String[])void which is correct. The exact form of the demangled string was discussed at greeat length in the thread http://gcc.gnu.org/ml/java-patches/2005-q3/msg00414.html. -- aph at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aph at gcc dot gnu dot org Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29044