On Tue, Mar 29, 2016 at 10:42 AM Aaron Ballman <aaron at aaronballman.com> wrote:> > Not everyone can upgrade to the latest version of the toolchain, even > if it has been released for a while. We did drop MSVC 2012 support > early, but MSVC 2015 was in RC or RTM stages by that point, and we had > some pretty big incentive to upgrade early (without function templates > supporting default arguments, the AST matcher DSL made for really slow > compiles of Clang itself, and resulted in a larger executable size > among other things, IIRC).I know you mentioned that one of the reasons we upgraded to 2013 was because 2015 was in RC or RTM. Ironically, the day after I posted this MS announced Visual Studio 15 preview <https://www.visualstudio.com/news/vs15-preview-vs> (which is confusingly the version *after* Visual Studio 2015). In any case, it's not an RC, and it's certainly not an RTM, but it is on the horizon. So hopefully we can revisit this question when 15 is in RC / RTM -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160331/d0eb1e5b/attachment.html>
On Thu, Mar 31, 2016 at 2:57 PM, Zachary Turner <zturner at google.com> wrote:> > > On Tue, Mar 29, 2016 at 10:42 AM Aaron Ballman <aaron at aaronballman.com> > wrote: >> >> >> Not everyone can upgrade to the latest version of the toolchain, even >> if it has been released for a while. We did drop MSVC 2012 support >> early, but MSVC 2015 was in RC or RTM stages by that point, and we had >> some pretty big incentive to upgrade early (without function templates >> supporting default arguments, the AST matcher DSL made for really slow >> compiles of Clang itself, and resulted in a larger executable size >> among other things, IIRC). > > > I know you mentioned that one of the reasons we upgraded to 2013 was because > 2015 was in RC or RTM. Ironically, the day after I posted this MS announced > Visual Studio 15 preview (which is confusingly the version *after* Visual > Studio 2015).Hah, that is confusing!> In any case, it's not an RC, and it's certainly not an RTM, > but it is on the horizon. So hopefully we can revisit this question when 15 > is in RC / RTMI think that's a great time to revisit the question (transitioning sometimes takes a bit of time since we want to ask people with out of tree needs if they're ready before dropping support for major releases). ~Aaron
https://www.visualstudio.com/en-us/news/vs2015-vs.aspx Is it time? 2016-03-31 12:03 GMT-07:00 Aaron Ballman via llvm-dev < llvm-dev at lists.llvm.org>:> On Thu, Mar 31, 2016 at 2:57 PM, Zachary Turner <zturner at google.com> > wrote: > > > > > > On Tue, Mar 29, 2016 at 10:42 AM Aaron Ballman <aaron at aaronballman.com> > > wrote: > >> > >> > >> Not everyone can upgrade to the latest version of the toolchain, even > >> if it has been released for a while. We did drop MSVC 2012 support > >> early, but MSVC 2015 was in RC or RTM stages by that point, and we had > >> some pretty big incentive to upgrade early (without function templates > >> supporting default arguments, the AST matcher DSL made for really slow > >> compiles of Clang itself, and resulted in a larger executable size > >> among other things, IIRC). > > > > > > I know you mentioned that one of the reasons we upgraded to 2013 was > because > > 2015 was in RC or RTM. Ironically, the day after I posted this MS > announced > > Visual Studio 15 preview (which is confusingly the version *after* > Visual > > Studio 2015). > > Hah, that is confusing! > > > In any case, it's not an RC, and it's certainly not an RTM, > > but it is on the horizon. So hopefully we can revisit this question > when 15 > > is in RC / RTM > > I think that's a great time to revisit the question (transitioning > sometimes takes a bit of time since we want to ask people with out of > tree needs if they're ready before dropping support for major > releases). > > ~Aaron > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160729/1a74cfb2/attachment.html>