public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Andrew Pinski" <pinskia@gmail.com>
To: "Dave MacLachlan" <dmaclach@google.com>
Cc: binutils@sourceware.org, gcc-patches@gcc.gnu.org,
	 	"DJ Delorie" <dj@delorie.com>,
	"Daniel Berlin" <dannyb@google.com>,
	 	"Mike Stump" <mrs@apple.com>
Subject: Re: binutils/libiberty patch for c++filt to demangle ObjC++ symbols
Date: Fri, 13 Apr 2007 17:27:00 -0000	[thread overview]
Message-ID: <de8d50360704131017m6177d258rc274a562c9a870a3@mail.gmail.com> (raw)
In-Reply-To: <31CDB327-F3DB-4884-95EF-98C247D70A2F@google.com>

On 4/13/07, Dave MacLachlan <dmaclach@google.com> wrote:
> This is a patch for c++filt so it can demangle ObjC++ symbols. Turns
> out that if you have an Objective C++ file (.mm) with a static var
> inside of a method it will get mangled in such a fashion that the
> current c++filt can't unmangle it:
>
> @implementation Foo
> + (void)bar:(id)sender {
>         static int baz = 1;
> }
> @end
>
> gets mangled to
>
> _ZZ11+[Foo bar:]E3baz


Actually I think this is the way it gets mangled on Darwin, I think it
gets mangled differently on any other target as the other targets
actually mangle the message name instead of keeping it as "+[Foo
bar:]".

So you might want to double check what happens under Linux with the
objective-C++ front-end also.

Thanks,
Andrew Pinski

  reply	other threads:[~2007-04-13 17:17 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 [this message]
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
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=de8d50360704131017m6177d258rc274a562c9a870a3@mail.gmail.com \
    --to=pinskia@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=dannyb@google.com \
    --cc=dj@delorie.com \
    --cc=dmaclach@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mrs@apple.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).