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: Ping: demangle C++ extern "C" functions


Thank you for your comments.

On Fri, 21 Oct 2011, Ian Lance Taylor wrote:

Marc Glisse <marc.glisse@inria.fr> writes:

_Z1aIFYviEEvPT_
void a<void (int) extern "C">(void (*)(int) extern "C")

Does g++ ever actually generate a symbol name like this? Is it worth worrying about?

g++ doesn't currently generate those, but I would like to change that (c++/2316). And nothing prevents another compiler from actually implementing the itanium C++ ABI (this code is mostly for binutils if I understand correctly).


I thought it made sense to submit independent pieces first, but if it is preferable to wait until everything is ready (not soon) I understand.

Personally if we are going to print this at all I think the extern "C"
should be in square brackets.  E.g.,

void a<void (int) [extern "C"]>(void (*)(int) [extern "C"])

Hey, that looks nice!


It doesn't look like attributes (in double square brackets) get mangled, so it shouldn't look strange (and it could always be changed in that case).

--
Marc Glisse


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