[Bug java/29044] Libiberty demangler can not handle new Java mangling.

2006-09-13 Thread drow at gcc dot gnu dot org
--- Comment #8 from drow at gcc dot gnu dot org 2006-09-13 12:31 --- Not a bug then. -- drow at gcc dot gnu dot org changed: What|Removed |Added Status|WAITIN

[Bug java/29044] Libiberty demangler can not handle new Java mangling.

2006-09-13 Thread drow at gcc dot gnu dot org
--- Comment #7 from drow at gcc dot gnu dot org 2006-09-13 12:31 --- Subject: Re: Libiberty demangler can not handle new Java mangling. > I don't understand why this bug has been reported. The bug was reported because the combination of the mangling change and the demangler postfix be

[Bug java/29044] Libiberty demangler can not handle new Java mangling.

2006-09-13 Thread aph at gcc dot gnu dot org
--- Comment #6 from aph at gcc dot gnu dot org 2006-09-13 09:01 --- I don't understand why this bug has been reported. Are you using an up-to-date libiberty to do the demangling? When I try c++filt --format java, I get Hello.main(java.lang.String[])void which is correct. The exact

[Bug java/29044] Libiberty demangler can not handle new Java mangling.

2006-09-13 Thread ian at airs dot com
--- Comment #5 from ian at airs dot com 2006-09-13 07:23 --- OK, with -s java I get jmain.main(java.lang.String[])void I misunderstood Daniel's report. Sorry about that. The fact that the function's return type is printed at the end is deliberate. This is because -s java sets DMGL

[Bug java/29044] Libiberty demangler can not handle new Java mangling.

2006-09-12 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-09-13 06:39 --- (In reply to comment #3) > When I run the demangler on > _ZN5jmain4mainEJvP6JArrayIPN4java4lang6StringEE > I get > void jmain::main(JArray*) What happens when running it in "Java" mode (note the -s java)? -

[Bug java/29044] Libiberty demangler can not handle new Java mangling.

2006-09-12 Thread ian at airs dot com
--- Comment #3 from ian at airs dot com 2006-09-13 06:36 --- When I run the demangler on _ZN5jmain4mainEJvP6JArrayIPN4java4lang6StringEE I get void jmain::main(JArray*) The relevant patch went in on 2005-12-10 to libiberty/cp-demangle.c. Can you confirm that you have that patch

[Bug java/29044] Libiberty demangler can not handle new Java mangling.

2006-09-12 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-09-13 04:03 --- (In reply to comment #0) > I am assuming the mangling change was deliberate. If so, the demangler should > be updated. The mangling change was to fix PR 9861. Maybe there is note linked from there about how this sh

[Bug java/29044] Libiberty demangler can not handle new Java mangling.

2006-09-12 Thread drow at gcc dot gnu dot org
--- Comment #1 from drow at gcc dot gnu dot org 2006-09-12 21:43 --- Unless this turns out to be a mangling problem, I assume it's a libiberty/demangler problem. -- drow at gcc dot gnu dot org changed: What|Removed |Added --