wide function pointer type

[Florian Weimer]

* Martin Uecker:

>> For GCC's nested function extension, there are no ABI concerns
>> because the nested function definition and the thunk generation are
>> always built from the same translation unit.  So GCC can just pick a
>> custom calling convention, similar to what it does for other local,
>> non-escaping functions.
>
> Yes, but there are many other languages that make use of the
> static chain.  So it would be good to have a standardized ABI
> for this.

What's the exact use case for this?  These other languages do not
usually have stable ABIs that inter-operate across different
implementations.

Thanks,
Florian