[PATCH] PR13457 (part 1) explicit/implicit calling conventions compatibility in overloads

Timur Iskhodzhanov timurrrr at google.com
Mon Mar 18 13:21:02 PDT 2013


What's the status?
I want this patch to be committed, but I'm not the right person to review it...

2013/3/6 Alexander Zinenko <ftynse at gmail.com>:
> Ping.
>
>
> On 2 March 2013 00:39, Alexander Zinenko <ftynse at gmail.com> wrote:
>>
>> Hello!
>>
>> This patch addresses the compatibility issue between explicitly specified
>> default calling conventions and implicit ones in overload resolution.  As of
>> now, such implicit conversions are only known in Microsoft ABI.  The
>> corresponding CodeGen already knows about these implicit defaults, so the
>> conversion kind could be just NoOp.
>>
>> The patch covers:
>> * pointers to free functions (__cdecl by default);
>> * references to free functions;
>> * pointers to static member functions and variadic member functions
>> (__cdecl by default);
>> * pointers to non-static non-variadic member functions (__thiscall by
>> default);
>> * simultaneous calling convention adjustment and base-to-derived implicit
>> conversion for member functions.
>>
>> The patch does not cover function templates, although the approach to this
>> is exactly the same as for PR15291.
>>
>> I suppose functions for determining calling convention compatibility could
>> be moved somewhere in TargetCXXABI if needed in other places.
>>
>> Please, review!
>> Suggestions are welcome.
>>
>> --
>> Alex
>
>
>
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
>



More information about the cfe-commits mailing list