This is the mail archive of the gcc-patches@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: [PATCH] PR libstdc++/13045 / C++ demangler, floating values and function pointer type return type postfix fix.


Gabriel Dos Reis <gdr@integrable-solutions.net> writes:

> Ian Lance Taylor <ian@wasabisystems.com> writes:
> 
> | Paul Koning <pkoning@equallogic.com> writes:
> | 
> | > I don't understand this -- code is built for a particular target.
> | > Why can't the demangler interpret floating point stuff according to
> | > what --target is set to?
> | 
> | The demangler has not historically been a target-dependent tool.  Such
> | a change would lead to things like renaming c++filt to TARGET-c++filt.
> 
> So, why not chose C9's hex floating notation?

The problem is not how to print the floating point value.  The problem
is how to interpret the floating point value which appears in the
mangled name.

Or, if you are suggesting that the mangling ABI be changed to use C99
hexadecimal floating point constants, then that sounds like a good
idea to me, certainly better than the current situation.  Of course,
it means that in some strange cases future g++ output will not be
link-compatible with current g++ output.

Ian


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