This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFA: Please review the new C++ demangler patch


"H. J. Lu" <hjl@lucon.org> writes:

>> >> I don't understand what you mean by "remove the old one".
>> >
>> > ar -d ..../libiberty.a cp-demangle.o
>> > ar rc ..../libiberty.a demangle.o
>> 
>> Ick.  There must be a better way.
>
> Any suggestions are welcome.

... build it as part of libiberty, after libstdc++, like I've been
trying to tell you?

and then we can GET RID OF the old demangler that doesn't work?

>> > The one in libiberty only supports the C interface without C++ support,
>> > like RTTI and exeception. Also it uses its own allocator and dynstring
>> > so that it can be used as a C function. Otherwise, you can put it in
>> > libiberty. But you don't want to do that in libstdc++.
>> 
>> Better we break up the demangler into "libiberty only" and "libstdc++
>> extra functionality", then.
>
> We have done that, but in .o files. You can have use both the demangler
> in libiberty and the one in libstdc++ in the same program.

Cleaner to do it at the source level, I think.

zw


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]