<div dir="ltr">Ping?</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 23 March 2013 01:22, Alexander Zinenko <span dir="ltr"><<a href="mailto:ftynse@gmail.com" target="_blank">ftynse@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi John, Joćo!</div><div><br></div><div>This patch adds a diagnostic if the following declarations have illegal calling conventions:</div>
<div>* pointer to function, reference to function, pointer to member function variable (or function attribute) declaration;</div>
<div>* function declaration;</div><div>* typedef declaration.</div><div><br></div><div>It was proposed in PR13457 discussion (<a href="http://llvm.org/bugs/show_bug.cgi?id=13457#c22" target="_blank">http://llvm.org/bugs/show_bug.cgi?id=13457#c22</a>).</div>
<div><br></div>We already have such error for variadic functions declared with CC_X86Fastcall that is emitted from SemaType. But microsoft ABI has different allowed CCs depending on whether it is a member function and it can't be determined given FunctionType only (AFAIK, standard doesn't differentiate between free function and member function types). So this checking has to be done on declarations.<div>
<br></div><div>With this patch, allowed calling conventions are ABI-specific. Therefore if we teach affected ABIs to disallow fastcall on variadic functions, we can remove the previous diagnostic.</div><div><br>
</div><div>Please review!</div><div><br></div><div>--</div><div>Alex</div></div>
</blockquote></div><br></div>