Instead of making this !FreeFunction-specific, can you compute the appropriate calling convention and do the unwrap/rewrap thing if it's different from the computed calling convention? I'd expect the same thing can happen for varargs function templates on some ABIs.
On Mon, Nov 18, 2013 at 8:05 AM, Rafael Espíndola < [email protected]> wrote: > Currently explicit template instatiations of member function templates > are failing with the microsoft abi an 32 bits. This happens because > the expected and computed function types have different calling > convention. > > This patch fixes it by considering the default calling convention for > methods in GetFullTypeForDeclarator. > > Cheers, > Rafael >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
