<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; "><br><div><div>On Oct 28, 2013, at 2:19 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">One thing I want to call out:</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 28, 2013 at 8:20 AM, Chris Lattner <span dir="ltr"><<a href="mailto:clattner@apple.com" target="_blank" class="cremed">clattner@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I suppose what I'm saying is that we are currently not using *any* C++'11 features. It seems like conservatively great progress for LLVM 3.4 to bump the minimum GCC requirement up to enable use of VC 2010-era features (like rvalue refs and simple stdlib features),</blockquote>
<div><br></div><div>I am strongly opposed to this. Currently, we have people that are relying on our C++98 status. This isn't actually about VC2010 issues, this is about GCC support. I think it would be a disservice to change that in 3.4, only a small number of weeks away from the branch point. That seems like very little notice.</div></div></div></div></blockquote><div><br></div><div>Yes, good point. A more logical one would be to go for 3.5/3.6 for "VC2010" and "VC2012" feature adoption.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><br></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "> then jump to VC2012 features in LLVM 3.5 assuming that goes well. We're talking about a 6 month delta between the two, and I think we'll learn a lot in the first step.</blockquote>
<div><br></div><div>I think the biggest jump will be to have a floor at all, and I think we should just pick on that makes sense, and advertise the day lights out of it. Put it in the 3.4 release notes that going forward we're going to be dropping support for older toolchains, etc., etc. This will really help manage the expectations of users, and ensure that folks plan adequately for 3.5 and get C++11-supporting toolchains installed on their systems, etc.</div>
<div><br></div><div>I have also heard no serious objection to the three versions I gave as a baseline: VC2012, GCC 4.7 (the series, not any specific patch release), and Clang 3.1.</div></div></div></div></blockquote><br></div><div>Ok. If no-one has an objection, then putting it in the release notes (and the announcement email!) makes sense. We can make the switch a few weeks after the release if no one has strongly objected.</div><div><br></div><div>-Chris </div><br></body></html>