From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17472 invoked by alias); 11 Jul 2003 00:36:37 -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 17459 invoked from network); 11 Jul 2003 00:36:36 -0000 Received: from unknown (HELO concert.shout.net) (204.253.184.25) by sources.redhat.com with SMTP; 11 Jul 2003 00:36:36 -0000 Received: from duracef.shout.net (duracef.shout.net [204.253.184.12]) by concert.shout.net (8.12.9/8.12.9) with ESMTP id h6B0aZop003181; Thu, 10 Jul 2003 19:36:35 -0500 Received: from duracef.shout.net (localhost [127.0.0.1]) by duracef.shout.net (8.12.9/8.12.9) with ESMTP id h6B0aZHK016996; Thu, 10 Jul 2003 19:36:35 -0500 Received: (from mec@localhost) by duracef.shout.net (8.12.9/8.12.9/Submit) id h6B0aZCI016995; Thu, 10 Jul 2003 20:36:35 -0400 Date: Fri, 11 Jul 2003 00:36:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200307110036.h6B0aZCI016995@duracef.shout.net> To: binutils@sources.redhat.com, hjl@lucon.org Subject: Re: FYI: A new C++ demangler Cc: gdb@sources.redhat.com X-SW-Source: 2003-07/txt/msg00148.txt.bz2 Summary: no regressions in the gdb test suite. One change detected that's a slight improvement. I know this is moot because gdb can't use code implemented in C++, but I thought it would be interesting to run the test anyways. I tested this with the usual: target => native host => i686-pc-linux-gnu osversion => red-hat-8.0 gdb => HEAD%20030708 gcc => 2.95.3, 3.2-7-rh, 3.3, gcc-3_3-branch%20030707, HEAD%20030707 binutils => 2.13.90.0.2-rh, 2.14, binutils-2_14-branch%20030707, HEAD%20030707 glibc => 2.2.93-5-rh gformat => dwarf-2, stabs+ glevel => 2 All the gcc v2 results were unchanged (obviously, since gdb still uses the same v2 demangler). The gcc v3 results were the same for all versions of gcc v3, binutils, and gformat. There were three places where something like this happened: # old print &'dm_type_unsigned_int' $6 = (int (*)(unsigned int)) 0x8048940 (gdb) PASS: gdb.c++/cplusfuncs.exp: detect dm_type_unsigned_int # new print &'dm_type_unsigned_int' $6 = (int (*)(unsigned int)) 0x8048940 (gdb) PASS: gdb.c++/cplusfuncs.exp: detect dm_type_unsigned_int That is, the old demangler prints 'unsigned' in some places, and the new demangler prints 'unsigned int'. This happened once in gdb.c++/cplusfuncs.exp and twice in gdb.c++/templates.exp. Michael C