public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@apple.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Dave MacLachlan <dmaclach@google.com>,
	binutils <binutils@sourceware.org>,
	        GCC Patches <gcc-patches@gcc.gnu.org>,
	DJ Delorie <dj@delorie.com>,
	        Daniel Berlin <dannyb@google.com>,
	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 07:01:00 -0000	[thread overview]
Message-ID: <27932321-3491-45D6-8F09-45FEE9D4F582@apple.com> (raw)
In-Reply-To: <de8d50360704252312s106a068bxfe7faaebd8367552@mail.gmail.com>


On Apr 25, 2007, at 11:12 PM, Andrew Pinski wrote:

> On 4/25/07, Eric Christopher <echristo@apple.com> wrote:
>>
>> 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).
>
> Well that and this is also a bug in the FSF GCC for darwin still as
> FSF GCC for darwin does the same thing as Apple's modified GCC does
> for this case.

Right, it's likely a darwin specific bug, but having an internal bug  
filed on it
is more likely to get it fixed :)

-eric

  reply	other threads:[~2007-04-26  6:13 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 [this message]
2007-04-26 19:19           ` Dave MacLachlan
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=27932321-3491-45D6-8F09-45FEE9D4F582@apple.com \
    --to=echristo@apple.com \
    --cc=binutils@sourceware.org \
    --cc=dannyb@google.com \
    --cc=dj@delorie.com \
    --cc=dmaclach@google.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).