Re: [boost] [type_traits] VC++ and vararg function/mmeber functions and varargs

Subject: Re: [boost] [type_traits] VC++ and vararg function/mmeber functions and varargs
From: Edward Diener (eldiener_at_[hidden])
Date: 2013-10-09 18:56:21

On 10/9/2013 3:51 PM, Stephan T. Lavavej wrote:
> [STL]
>> __vectorcall can be applied to member functions.
>
> [Edward Diener]
>> http://msdn.microsoft.com/en-us/library/vstudio/dn375768%28v=vs.120%29.aspx
>> "Using the /Gv compiler option causes each function in the module to
>> compile as __vectorcall unless the function is a member function, is
>> declared with a conflicting calling convention attribute, uses a vararg
>> variable argument list, or has the name main."
>
> That's different.
>
> What I said is that __vectorcall can be applied to member functions, i.e. directly. What MSDN is saying is that /Gv changes the default calling convention to __vectorcall for non-member functions, but doesn't affect member functions.

OK. It does seem odd that __vectorcall can be applied to member 
functions but your compiler option for __vectorcall does not apply to 
member functions.

Thanks for the clarification.