C++ ABI: Mangling of call_expr

[Giovanni Bajo]

Nathan Sidwell <nathan@codesourcery.com> wrote:

>> But what is a CALL_EXPR? Its two-letter mangled name is "cl", but it
>> certainly can't be either unary, binary, or trinary. In fact, in
>> operators.def, it is defined with arity "-1", which means "any arity is
>> allowed". But then, I can't see which production is supposed to use.

> looks like a bug in the ABI spec. To be demanglable, there must be a count
> of the number of parameters encoded.
> Mark, have I missed something?

Since we are at it, I think the ABI is also missing a description of how to
mangle a call to a constructor.

Giovanni Bajo