analysis of libiberty/cp-demangle.c for libsupc++/__cxa_demangle

[Mark Mitchell]

Ian Lance Taylor wrote:

> Mark Mitchell <mark@codesourcery.com> writes:
> 
> 
>>>The ABI says that an ambiguity
>>>between an extern "C" name and an internal built-in type name should
>>>be resolved in favor of the extern "C" name.  It doesn't say what to
>>>return for an extern "C" name.  That is, it doesn't say that
>>>__cxa_demangle() should return "i" when passed "i".
>>
>>That's a clever reading.  I'm not sure it's what was intended, but
>>then again I'm not sure that this particular interface was thought
>>through very well at all.  We stayed away from these kinds of corner
>>cases in our ABI testsuite because it was indeed unclear what should
>>be done.
> 
> 
> To aid my understanding of the backstory here, who wrote the ABI in
> the first place?

It was a coalition of people.  Jim Denhert wrote many of the words, with 
lots of input from Matt Austern, Christophe de Dinechin, Martin von 
Loewis, Jason Merill, Alex Samuel, Daveed Vandervoode, myself, and lots 
of other people I'm forgetting.  However, the process was pretty 
informal; it's not like these were ISO meetings.  It wsa a lot of 
hanging out in SGI's conference rooms and drawing on whiteboards.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com