C++ ABI: Mangling of call_expr

[Andreas Schwab]

"Giovanni Bajo" <giovannibajo@libero.it> writes:

|> Hello,
|> 
|> I can't understand how mangle.c is supposed to mangle a call expression.
|> Currently, it just segfaults on it. The expression production from the ABI
|> says:
|> 
|> <expression> ::= <unary operator-name> <expression>
|>             ::= <binary operator-name> <expression> <expression>
|>             ::= <trinary operator-name> <expression> <expression>
|> <expression>
|> [...]
|> 
|> 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.

A function call is actually a postfix expression.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."