This has reached mozilla-central and nightlies are now being built with VS2017.
The clang-cl builds (which still rely on a VS package for link.exe, among other things) remain on VS2015 while I work out some issues in clang-cl's path detection. All other Windows jobs have moved to VS2017. While I'm here, I want to give a shout out to everyone who helped with the move to Taskcluster and in-tree job definitions. In previous compiler upgrades I had to beg for a lot of handholding from busy releng folks. This time was an absolute piece of cake. Everything was self-explanatory, self-service, and easily testable on Try. Thank you! On Wed, Oct 25, 2017 at 5:48 PM, David Major <dma...@mozilla.com> wrote: > I'm planning to move production Windows builds to VS2017 (15.4.1) in bug > 1408789. > > VS2017 has optimizer improvements that produce faster code. I've seen 3-6% > improvement on Speedometer. There is also increased support for C++14 and > C++17 language features: https://docs.microsoft.com/en- > us/cpp/visual-cpp-language-conformance > > These days we tend not to support older VS for too long, so after some > transition period you can probably expect that VS2017 will be required to > build locally, ifdefs can be removed, etc. VS2017 Community Edition is a > free download and it can coexist with previous compilers. Installation > instructions are at: https://developer.mozilla.org/ > en-US/docs/Mozilla/Developer_guide/Build_Instructions/ > Windows_Prerequisites#Visual_Studio_2017 > > If you have concerns, please talk to me or visit the bug. Thanks! > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
