Marc Glisse writes:
> 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 in
Thank you for your comments.
On Fri, 21 Oct 2011, Ian Lance Taylor wrote:
Marc Glisse writes:
_Z1aIFYviEEvPT_
void a(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 c
Marc Glisse writes:
>> _Z1aIFYviEEvPT_
>> void a(void (*)(int) extern "C")
Does g++ ever actually generate a symbol name like this? Is it worth
worrying about?
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) [ex
Ping (changing the Cc to bother a different person...).
On Sat, 3 Sep 2011, Marc Glisse wrote:
Hello,
this patch is obviously related to PR c++/2316 ("g++ fails to overload on
language linkage") but seems fairly independent. Currently, the demangler
recognizes 'Y' for extern "C" functions a
Hello,
this patch is obviously related to PR c++/2316 ("g++ fails to overload on
language linkage") but seems fairly independent. Currently, the demangler
recognizes 'Y' for extern "C" functions and ignores it. The patch makes it
print extern "C" after the function type:
_Z1aIFYviEEvPT_
void
