<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 22, 2014, at 9:53 AM, Daniel Dilts <<a href="mailto:diltsman@gmail.com" class="">diltsman@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Fri, Aug 22, 2014 at 9:42 AM, Chris Bieneman <span dir="ltr" class=""><<a href="mailto:beanz@apple.com" target="_blank" class="">beanz@apple.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div class="">Starting a new thread to loop in cfe-dev and lldb-dev. For those not following along there has been a thread on llvm-dev about moving the minimum required Visual Studio version to 2013. The motivating reason is this will allow us to take advantage of a bunch of C++11 features that are not supported by MSVC 2012.<br class="">
</div></blockquote><div class=""><br class=""></div><div class="">Is there an existing policy on how supported compiler versions are selected? </div></div></div></div>
</div></blockquote></div><br class=""><div class="">There was a discussion last year (<a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/066847.html" class="">http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/066847.html</a>) WRT allowing LLVM to use C++11 features which established a precedent of supporting compilers released back for two years, with a special caveat for Windows.</div><div class=""><br class=""></div><div class="">-Chris</div></body></html>