RKSimon added a comment. In D114639#3162000 <https://reviews.llvm.org/D114639#3162000>, @mehdi_amini wrote:
> In D114639#3161303 <https://reviews.llvm.org/D114639#3161303>, @erichkeane > wrote: > >> IMO, if we're updating the MSVC versions, we should do the same for the >> GCC/Clang/AppleClang versions too. For example, GCC 5.1 is from 2015, and >> Clang 3.5 is from 2014. > > We've always handled MSVC update separately I believe, we can't just take the > "last two version of MSVC" guideline and update every compiler each time. > (I'm not against updating our toolchain to support c++17, but that's > orthogonal to the MSVC-specific update) I recently started a C++17 conversation here, but I agree its orthogonal to the VS version bump: https://lists.llvm.org/pipermail/llvm-dev/2021-November/153882.html Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D114639/new/ https://reviews.llvm.org/D114639 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
