On Wed, Oct 25, 2017, at 05:48 PM, David Major wrote: > I'm planning to move production Windows builds to VS2017 (15.4.1) in bug > 1408789.
Thanks for doing the work on this! > 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 Lately we've settled on maintaining support for ~1 release cycle, which gives us a buffer before we rip out support in case we need to roll back because we've found a major compiler bug or something like that. It's easier to justify maintaining support if we have CI to ensure that we're not constantly breaking things. On the other hand, it's easier to justify dropping support if VS is the last compiler holding us back from being able to use new C++ features. -Ted _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
