Demangling broken (was: Re: [PATCH] Demangler woes with current CVS and type names)

Daniel Jacobowitz drow@mvista.com
Thu Jan 31 20:10:00 GMT 2002


On Thu, Jan 31, 2002 at 06:22:31PM -0500, Daniel Jacobowitz wrote:
> On Thu, Jan 31, 2002 at 04:36:00PM -0500, Phil Edwards wrote:
> > On Thu, Jan 31, 2002 at 07:28:55PM +0100, Hans-Peter Nilsson wrote:
> > > > Does it ever make sense for any demangling anywhere -- i.e., for non-types --
> > > > to only partially consume a mangled string?  (I wouldn't think so, but...)
> > > 
> > > I don't know either, but supposedly it can stop at characters
> > > not in the mangled set.  I don't remember if it has to eat all
> > > characters fed to it to be considered successful.
> > 
> > Hmm.  Okay, I won't go that route.
> > 
> > 
> > > Either way seems a partial solution, solving the "data" ->
> > > "double" error, but not to the "d" -> "double" error.
> > 
> > Ah, I see the problem more clearly now; thanks.  Yes, it looks like an option
> > is needed.  I'll look into some kind of "no type demangling" flag somewhere.
> 
> Please go the other way.  This is an incompatible interface change -
> and you've seen the violence you did to GDB and LD testsuites with this
> patch by now, right?

Sorry for my tone and lack of clarity there.  By "the other way" I
meant "Yes, a flag to control this would be a great idea, but please
use a 'type demangling' flag rather than a 'no type demangling' flag."

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer



More information about the Binutils mailing list