From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18593 invoked by alias); 26 Apr 2007 17:56:09 -0000 Received: (qmail 18582 invoked by uid 22791); 26 Apr 2007 17:56:08 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 26 Apr 2007 18:56:07 +0100 Received: from zps78.corp.google.com (zps78.corp.google.com [172.25.146.78]) by smtp-out.google.com with ESMTP id l3QHtpDg001509; Thu, 26 Apr 2007 10:55:53 -0700 Received: from [172.18.101.109] (viper.corp.google.com [172.18.101.109]) (authenticated bits=0) by zps78.corp.google.com with ESMTP id l3QHstD6013967 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 26 Apr 2007 10:54:55 -0700 In-Reply-To: <3F248524-3F5F-4CC2-9895-201DC4C96F9A@apple.com> References: <27E8A691-807E-4CB5-A7EE-6A3FAC4013A1@google.com> <200704130412.l3D4CbdI024712@localhost.localdomain> <31CDB327-F3DB-4884-95EF-98C247D70A2F@google.com> <79E2C699-C52B-469D-A836-A7BA91E4E275@google.com> <3F248524-3F5F-4CC2-9895-201DC4C96F9A@apple.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <587D7DDB-C21F-4564-9573-02B43DA90569@google.com> Cc: Andrew Pinski , binutils , GCC Patches , Mike Stump , Fariborz Jahanian Content-Transfer-Encoding: 7bit From: Dave MacLachlan Subject: Re: binutils/libiberty patch for c++filt to demangle ObjC++ symbols Date: Thu, 26 Apr 2007 19:19:00 -0000 To: Eric Christopher X-Mailer: Apple Mail (2.752.3) X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00355.txt.bz2 On Apr 25, 2007, at 23:08 , Eric Christopher wrote: >> >> Andrew... >> >> You are 100% correct. Should I change the option then from ObjC++ >> to AppleObjC++ or do we hope that they are going to be changing >> their mangling to be C++ compliant? >> >> Other options? > > I'd hope the ObjC++ mangling should be C++ compliant. Do you have > access to the apple bug reporter (radar) so you can enter it there? > (If not, let me know and I'll file it). > > -eric Radar 5129938 "c++filt does not deal with ObjC++ symbols" is close. Do you want me to log a different one? Cheers, Dave