--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28797
--- Comment #9 from ian at airs dot com 2006-08-27 21:44 ---
I'm going to close this PR since I just fixed the only real problem that I see
here. If you see other problems with the demangler, please open a separate PR
for each problem.
Thanks for reporting the bug.
--
ian at airs d
--- Comment #8 from ian at gcc dot gnu dot org 2006-08-27 21:43 ---
Subject: Bug 28797
Author: ian
Date: Sun Aug 27 21:42:55 2006
New Revision: 116493
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116493
Log:
PR other/28797
* cp-demangle.c (d_pointer_to_member_t
--- Comment #7 from ian at airs dot com 2006-08-26 19:04 ---
I am testing a patch to the demangler to correctly handle _Z1fM1AKiPKS1_.
--
ian at airs dot com changed:
What|Removed |Added
-
--- Comment #6 from ian at airs dot com 2006-08-26 18:54 ---
OK, so that's where you got your symbols, but where did you get your list of
demangled strings? Did you just compare directly to the source code? Or are
you using some other demangler?
--
http://gcc.gnu.org/bugzilla/show
--- Comment #5 from kurkov at gorodok dot net 2006-08-25 08:50 ---
(In reply to comment #4)
> Where did you get your list of symbol names and demangled strings?
My program uses C standard I/O routines instead of iostreams, to support
new-ABI C++ compilers that do not have complete C++ st
--- Comment #4 from ian at airs dot com 2006-08-24 06:20 ---
Where did you get your list of symbol names and demangled strings?
As Andrew has pointed out, there seem to be a few different issues here:
different spacing, different qualifier order, different handling of floating
point con
--- Comment #3 from kurkov at gorodok dot net 2006-08-22 05:52 ---
(In reply to comment #1)
Sorry for space and unsigned int issues, I should just correct compare files
for my test.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28797
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-08-22 05:26 ---
(In reply to comment #1)
> The double ones are weird, maybe we should print out the C99 hex float
> instead,
> there is a bug about this before too.
See PR 13045, there is most likely more discussion about this.
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-08-22 05:21 ---
_Z1fA37_iPS_ -> f(int [37], int (*) [37]), should be: f(int[37], int (*) [37])
Isn't that just a space?
_Z1fILi2EEvRAplplT_Li3ELi1E_i -> void f<2>(int (&) [((2) + (3)) + (1)]), should
be: void f<2>(int (&) [((2)+(3)
10 matches
Mail list logo
