<div dir="ltr">I'd like to revisit this. As a person who spends a fair amount of time monitoring our VS 2013 buildbots, I would say that I am ready to throw in the towel on MSVC 2013. Since this discussion, I have committed five (!) workarounds for MSVC 2013:<br><div><br></div><div># in llvm</div><div>$ git log --author=rnk --grep=2013 --after='Aug 4 2016' --oneline<br></div><div><div>21a8ade Fix the MSVC 2013 build by using Elf_Word instead of making a local typedef</div><div>27e101d Revert "Add an optional parameter with a list of undefs to extendToIndices"</div><div>e8beddd Make vec_fabs.ll pass with MSVC 2013</div><div>ca77873 [AMDGPU] Give enum an explicit 64-bit type to fix MSVC 2013 failures</div></div><div><div><br></div><div># in clang</div><div><div>$ git log --author=rnk --grep=2013 --after='Aug 4 2016' --oneline</div><div>18235a5 Try to work around an MSVC 2013 bug around defaulted default ctors</div></div></div><div><br></div><div>I'm pretty sure I'm missing instances where I helped others commit workarounds as well. So, I'd really like to drop 2013, probably sometime next month.</div><div><br></div><div>That said, I'd also like to echo Paul's sentiment that it'd help if people were less adventurous in their uses of C++11. New language features may look nice, but ultimately you may end up wasting my time and yours when I come and revert your change.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 4, 2016 at 7:52 AM, Robinson, Paul via llvm-dev <span dir="ltr"><<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div class="m_3760963737388214087WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I've heard from another group within Sony that they had "a number of problems" with VS2015 update 2, and strongly recommend going straight to update 3. My
immediate team has initiated a request but it hasn't gone through yet.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">--paulr<u></u><u></u></span></p>
<p class="MsoNormal"><a name="m_3760963737388214087__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> James Molloy [mailto:<a href="mailto:james@jamesmolloy.co.uk" target="_blank">james@jamesmolloy.co.<wbr>uk</a>]
<br>
<b>Sent:</b> Wednesday, August 03, 2016 1:54 AM<br>
<b>To:</b> Nico Weber; Robinson, Paul<br>
<b>Cc:</b> llvm-dev; <a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><span class=""><br>
<b>Subject:</b> Re: [cfe-dev] [llvm-dev] Revisiting our informal policy to support two versions of MSVC<u></u><u></u></span></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi,<u></u><u></u></p><div><div class="h5">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">This sounds like a decent idea to me. However we use 2013 for all our windows builds at the moment and it will take around 2 weeks to upgrade the installations on our cluster. We're pushing this hard to get it done soon so we don't get
caught short, but a grace period would be much appreciated.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Cheers,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">James<u></u><u></u></p>
</div>
</div></div></div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Tue, 2 Aug 2016 at 21:24 Nico Weber via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal">On Tue, Aug 2, 2016 at 3:49 PM, Robinson, Paul via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="color:#222222">For my project, timing is everything. We (and I could easily imagine,</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal">for many downstream projects) lead time is important.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">In Chromium land, we've so far been able to use the same compiler we use to build Chrome to build clang. Currently that's MSVS2015 update 2, and it took quite a while to update from 2013 to 2015 due bugs in 2015 and whatnot. So I agree
that it's useful to support older MSVS versions for some time. For this reason, requiring update 3 would be inconvenient for us, but 2015u2 would be no problem by now. It would've been a problem if 2015 had been required shortly after it was released.<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Nico<u></u><u></u></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal">______________________________<wbr>_________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/cfe-dev</a><u></u><u></u></p>
</blockquote>
</div>
</div></div></div>
</div>
</div>
<br>______________________________<wbr>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><br>
<br></blockquote></div><br></div>