This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
[Bug java/29044] New: Libiberty demangler can not handle new Java mangling.
- From: "drow at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: java-prs at gcc dot gnu dot org
- Date: 12 Sep 2006 21:33:38 -0000
- Subject: [Bug java/29044] New: Libiberty demangler can not handle new Java mangling.
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
In earlier versions of GCJ this:
public class jmain
{
public static void main (String[] args)
{
return;
}
}
Was mangled to:
_ZN5jmain4mainEP6JArrayIPN4java4lang6StringEE
Now it is mangled to:
_ZN5jmain4mainEJvP6JArrayIPN4java4lang6StringEE
(Including Jv, for a void return type).
This can't be properly demangled (use a current c++filt -s java):
jmain.main(java.lang.String[])void
I am assuming the mangling change was deliberate. If so, the demangler should
be updated.
--
Summary: Libiberty demangler can not handle new Java mangling.
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: drow at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29044