Displaying 2 results from an estimated 2 matches for "21510e3e".
2016 Sep 01
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
...ar. If it doesn't, and supporting 2015 and "15" at the same time has the
same cost, then we won't bother raising the floor for a while.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160901/21510e3e/attachment.html>
2016 Sep 01
3
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
I guess what I'm getting at, is why do we even need to support 2 toolchains
with LLVM *at all*? Why can't we just always upgrade to the newest one
unless there are serious issues with it?
There used to be two reasons that I'm aware of:
1) Licensing. Community used to be Express, and Express used to be limited
in functionality. But this is no longer the case. Community is fine for