[llvm-dev] Upgrading to MSVC 2015

[Alexander Riccio via llvm-dev]

Btw, I can't remember if this is explicit in the documentation: Does LLVM require the latest two *updated* versions of Visual Studio? (i.e. VS2013 update 5 & VS 2015 update 1)

I've seen people on the mailing list several times running an out of date version, which is nonsensical, and could cause strange problems.

sent from my (stupid) windows phone

-----Original Message-----
From: "Zachary Turner via llvm-dev" <llvm-dev at lists.llvm.org>
Sent: ‎3/‎29/‎2016 1:30 PM
To: "llvm-dev" <llvm-dev at lists.llvm.org>
Subject: [llvm-dev] Upgrading to MSVC 2015

I think it's been a little over a year since we bumped the minimum VS version to 2013.  Are we planning to do the same for 2015?  Update 2 is releasing soon, which is stable enough at least to ship Chromium.


Language wise, 2015 comes with a lot of new C++ features.  The most interesting to people will probably be template aliases, C++11 constexpr, the thread_local keyword, and thread-safe function local statics (finally).  A complete list of new C++ language support can be found here.


As far as the different LLVM subprojects are concerned, LLDB was always going to be the hardest get working with MSVC 2015 due to the fact that it embeds python as an extension module, but as the LLDB maintainer for Windows I tackled this early and I can say that it's now done and we have completely transitioned to MSVC 2015 already in LLDB.


Since we are only supporting 2015 in LLDB moving forward, I have a slight preference to bumping this in LLVM sooner rather than later, but I'd like to hear other peoples' thoughts on the matter as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160329/b1254e0f/attachment.html>