From: Ian Lance Taylor <ian@wasabisystems.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb@sources.redhat.com, tromey@redhat.com
Subject: Re: demangler, java, clinit, $E
Date: Sat, 20 Dec 2003 15:55:00 -0000 [thread overview]
Message-ID: <m3y8t71o2v.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20031217002907.3CA854B375@berman.michael-chastain.com>
mec.gnu@mindspring.com (Michael Elizabeth Chastain) writes:
> There are also 127 names which did not demangle at all, even with
> "--format java". This happens with both old and new demangler.
> These worry me. I have appended the list.
...
> _ZN3org3xml3sax7helpers11NewInstance6class$$EPN4java4lang6StringE
I checked a patch into the gcc repository to demangle this sort of
name, in which the Java mangler inserted a '$' which is not counted in
the identifier length.
As I said in my message to gcc-patches:
As a side note, my guess is that adding the '$' is intended to make it
possible for Java routines to be implemented in C++. The C++ code
would simply append a '$' to the keyword, in order to be able to use
it in C++. Unfortunately, this won't work, because the C++ mangler
will count the '$' in the identifier length, unlike the Java mangler.
So if my guess about the intention is correct, then this is actually a
bug in the Java mangler. If the Java mangler is fixed to count the
'$' in the identifier length, then the patch below will only be needed
for older code. It will do no harm for newer code, except that in
extremely unusual situations it will demangle a symbol name which is
not actually a mangled name.
Ian
prev parent reply other threads:[~2003-12-20 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 0:29 Michael Elizabeth Chastain
2003-12-17 3:52 ` Ian Lance Taylor
2003-12-17 16:17 ` Tom Tromey
2003-12-17 17:22 ` Ian Lance Taylor
2003-12-20 15:55 ` Ian Lance Taylor [this message]
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=m3y8t71o2v.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=tromey@redhat.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