public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: maynardj@us.ibm.com
Cc: binutils@sourceware.org
Subject: Re: C++ demangling of 64-bit symbols on ppc64
Date: Thu, 05 Apr 2007 01:04:00 -0000	[thread overview]
Message-ID: <m3abxn3a3r.fsf@localhost.localdomain> (raw)
In-Reply-To: <4612D2FA.4050407@us.ibm.com>

Maynard Johnson <maynardj@us.ibm.com> writes:

> As the de facto maintainer of the ppc64 bits of oprofile, I was
> recently asked to look into an oprofile bug where it was incorrectly
> demangling 64-bit symbols.  The oprofile code uses the libiberty
> function, cplus_demangle(), but is not getting back the right answer
> for ppc64 64-bit symbols.  This appears to be more fallout from the
> change (made a couple years ago or so) to the opd for ppc64, where the
> leading "." was removed from 64-bit symbols.
> 
> I hacked around the problem in my private oprofile src tree, but I'm
> thinking this issue should be solved at its source.  I'm seeing this
> problem on a SLES 10 system with binutils version 2.16.91.  Has this
> possibly been resolved in a more recent binutils version or in CVS?

Can you give an example of a symbol which the demangler is not
handling correctly?

Ian

  reply	other threads:[~2007-04-05  1:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 22:19 Maynard Johnson
2007-04-05  1:04 ` Ian Lance Taylor [this message]
2007-04-05 13:10   ` Maynard Johnson
2007-04-05 16:00     ` Ian Lance Taylor
2007-04-05 19:16       ` Maynard Johnson
2007-04-06  0:55         ` Ian Lance Taylor

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=m3abxn3a3r.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=maynardj@us.ibm.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).