From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19485 invoked by alias); 18 Apr 2003 19:47:02 -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 19478 invoked from network); 18 Apr 2003 19:47:02 -0000 Received: from unknown (HELO dberlin.org) (69.3.5.6) by sources.redhat.com with SMTP; 18 Apr 2003 19:47:02 -0000 Received: from [192.168.1.31] (account dberlin HELO dberlin.org) by dberlin.org (CommuniGate Pro SMTP 4.1b3) with ESMTP-TLS id 3582839; Fri, 18 Apr 2003 15:47:01 -0400 Date: Fri, 18 Apr 2003 19:47:00 -0000 Subject: Re: [RFA] handling of 'operator' in cp_find_first_component Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: gdb-patches@sources.redhat.com, Daniel Jacobowitz To: David Carlton From: Daniel Berlin In-Reply-To: Message-Id: <804F2BCA-71D6-11D7-8CF6-000393575BCC@dberlin.org> Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00351.txt.bz2 On Friday, April 18, 2003, at 03:17 PM, David Carlton wrote: > The function cp_find_first_component assumes that the string > 'operator' as part of an operator name can only occur at the start of > a component. Unfortunately, this isn't true: I've recently run into > situations where there's a templated function whose name demangles to > something like > > int operator<< (char) > > In particular, the return type is part of the demangled name (I'm not > entirely sure why, but that's a separate issue), Templated functions always have the return type in the mangled (and thus, demangled) names. We've actually been through this before, they are supposed to be there. see http://sources.redhat.com/ml/gdb/2001-06/msg00227.html (I quote the relevant part of the ABI standard)