<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 19 August 2016 at 15:56, Reid Kleckner <span dir="ltr"><<a href="mailto:rnk@google.com" target="_blank">rnk@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">I don't think we can change the ordering because VC/include is typically included in the INCLUDE environment variable, and that directory contains MSVC's *mmintrin.h headers, which are compiler-specific. We need clang's intrinsic headers to win out over MSVC's.</div></div></div></blockquote><div><br></div><div>OK, that sounds like a plausible excuse! :-)</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"> It sounds like you can work around the issue by passing /I., though, right?</div></div></div></blockquote><div><br></div><div>Yes, there are plenty of easy workarounds.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Thanks for the report, though, always excited to hear about new user experiences. :)</div></div></div></blockquote><div><br></div><div>Overall the transition from cl to clang-cl was incredibly smooth. Thanks!</div><div><br></div><div>For the record, the only other problem I ran into that I haven't seen mentioned elsewhere is that cl (as of VS 2015) accepts _try/_except as synonyms for __try/__except, even though it's more or less explicitly documented that they <i>don't</i> exist!</div><div><br></div><div><a href="https://msdn.microsoft.com/en-us/library/2e6a4at9.aspx">https://msdn.microsoft.com/en-us/library/2e6a4at9.aspx</a><br></div><div>"<span style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif">For backward compatibility, single-underscore versions of all the double-underscored keywords except </span><strong style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif">__except</strong><span style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif">,</span><strong style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif">__finally</strong><span style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif">, </span><strong style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif">__leave</strong><span style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif">, and </span><strong style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif">__try</strong><span style="font-size:13px;color:rgb(42,42,42);font-family:"Segoe UI","Lucida Grande",Verdana,Arial,Helvetica,sans-serif"> are supported.</span>"</div><div><br></div><div>Jay.</div></div></div></div>