From: Dave MacLachlan <dmaclach@google.com>
To: Eric Christopher <echristo@apple.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
binutils <binutils@sourceware.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Mike Stump <mrs@apple.com>,
Fariborz Jahanian <fjahanian@apple.com>
Subject: Re: binutils/libiberty patch for c++filt to demangle ObjC++ symbols
Date: Thu, 26 Apr 2007 19:19:00 -0000 [thread overview]
Message-ID: <587D7DDB-C21F-4564-9573-02B43DA90569@google.com> (raw)
In-Reply-To: <3F248524-3F5F-4CC2-9895-201DC4C96F9A@apple.com>
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
next prev parent reply other threads:[~2007-04-26 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <27E8A691-807E-4CB5-A7EE-6A3FAC4013A1@google.com>
[not found] ` <200704130412.l3D4CbdI024712@localhost.localdomain>
2007-04-13 17:07 ` Dave MacLachlan
2007-04-13 17:27 ` Andrew Pinski
2007-04-20 0:02 ` Dave MacLachlan
2007-04-26 6:12 ` Eric Christopher
2007-04-26 6:13 ` Andrew Pinski
2007-04-26 7:01 ` Eric Christopher
2007-04-26 19:19 ` Dave MacLachlan [this message]
2007-04-27 0:33 ` Eric Christopher
2007-04-27 3:35 ` Dave MacLachlan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=587D7DDB-C21F-4564-9573-02B43DA90569@google.com \
--to=dmaclach@google.com \
--cc=binutils@sourceware.org \
--cc=echristo@apple.com \
--cc=fjahanian@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mrs@apple.com \
--cc=pinskia@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).