search for: msc17

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. According to MSDN (http://msdn.microsoft.com/en-us/library/hh567368.aspx) the list is:

> Here is a trivial reason why I have not propagated http://bb.pgr.jp/ . > Sometimes (but I suppose rarely) he reports false alarm in a few > points. He'd send blames to the llvm-testresults if his master (aka I) > knew he were mature. > > I don't also want him promoted and called as one of official > buildbots. He is my pet, though, I expect he should be helpful to

Here is a trivial reason why I have not propagated http://bb.pgr.jp/ . Sometimes (but I suppose rarely) he reports false alarm in a few points. He'd send blames to the llvm-testresults if his master (aka I) knew he were mature. I don't also want him promoted and called as one of official buildbots. He is my pet, though, I expect he should be helpful to the developers. ...Takumi

...in order to not require > /bigobj support (see http://reviews.llvm.org/D5485). This change > relies on function templates with default arguments, which MSVC does > not support (it generates a C4519 error in MSVC 2012), resulting in > red bots (http://bb.pgr.jp/builders/ninja-clang-i686-msc17- > R/builds/10721). I have a sad bot failing to build in Debug mode, glad to know there's a fix in the works. > > This is a considerably more interesting case (at least to me) than > hypothetical benefits -- if we retain MSVC 2012 support, we will also > require /bigobj suppor...