[cfe-dev] [llvm-dev] Revisiting our informal policy to support two versions of MSVC
Robinson, Paul via cfe-dev
cfe-dev at lists.llvm.org
Thu Aug 4 07:52:42 PDT 2016
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.
From: James Molloy [mailto:james at jamesmolloy.co.uk]
Sent: Wednesday, August 03, 2016 1:54 AM
To: Nico Weber; Robinson, Paul
Cc: llvm-dev; cfe-dev at lists.llvm.org
Subject: Re: [cfe-dev] [llvm-dev] Revisiting our informal policy to support two versions of MSVC
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.
On Tue, 2 Aug 2016 at 21:24 Nico Weber via cfe-dev <cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>> wrote:
On Tue, Aug 2, 2016 at 3:49 PM, Robinson, Paul via cfe-dev <cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>> wrote:
For my project, timing is everything. We (and I could easily imagine,
for many downstream projects) lead time is important.
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.
cfe-dev mailing list
cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev