search for: hh567368

I’d like to propose raising the minimum required compiler for the LLVM & Clang trunks for Visual Studio to MSVC 2013. Doing 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: * Non-static data member initializers * Variadic templates * Initializer lists * Default template arguments for function templates * Expression SFINAE * Alias templates * Delegating constructors * Explicit conversion operators * Raw string literals * Defaulted and deleted functi...

...g the minimum required compiler for the LLVM & > Clang trunks for Visual Studio to MSVC 2013. > > > > Doing 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: > > > > * Non-static data member initializers > > * Variadic templates > > * Initializer lists > > * Default template arguments for function templates > > * Expression SFINAE > > * Alias templates > > * Delegating constructors >...

...> Clang trunks for Visual Studio to MSVC 2013. > >> > > >> > Doing 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: > >> > > >> > * Non-static data member initializers > >> > * Variadic templates > >> > * Initializer lists > >> > * Default template arguments for function templates > >> > * Expression SFINAE > >> &...

...owing 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: * Non-static data member initializers * Variadic templates * Initializer lists * Default template arguments for function templates * Expression SFINAE * Alias templates * Delegating constructors * Explicit conversion operators * Raw string literals * Defaulted and deleted functi...

Here is a table detailing C++11 features support for Visual C++ 2010, 2012, 2013 http://msdn.microsoft.com/en-us/library/vstudio/hh567368.aspx Specifically, range-based for loops are supported in Visual C++ 2012, 2013 but not in 2010. Yaron 2013/10/28 David Tweed <david.tweed at gmail.com> > On Mon, Oct 28, 2013 at 9:00 AM, Óscar Fuentes <ofv at wanadoo.es> wrote: > >> Dix Lorenz <lists at dix-lorenz....

...io to MSVC 2013. >> >> > >> >> > Doing 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: >> >> > >> >> > * Non-static data member initializers >> >> > * Variadic templates >> >> > * Initializer lists >> >> > * Default template arguments for function templates >> >> > * Expressio...

On Jan 9, 2013, at 3:03 AM, Óscar Fuentes <ofv at wanadoo.es> wrote: > Chris Lattner <clattner at apple.com> writes: > >> Wow, requiring GCC 4.7 would be really aggressive, it was just >> released in March 2012. Call me conservative, but I was thinking that >> a reasonable GCC baseline would be GCC 4.4 or something (which is ~3.5 >> years old). >

On Mon, Oct 28, 2013 at 9:00 AM, Óscar Fuentes <ofv at wanadoo.es> wrote: > Dix Lorenz <lists at dix-lorenz.de> writes: > > > I might be mistaken, but to compile for WinXP on VS 2012 you have to > > switch the Platform Toolset and AFAICT that means it will essentially > > be using the VS 2010 compiler and libraries. > > That was how VS 2012 worked at

...out 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: > > > > * Non-static data member initializers > > * Variadic templates > > * Initializer lists > > * Default template arguments for function templates > > * Expression SFINAE > > * Alias templates > > * Delegating constructors >...

Hello, Today we hit another VS 2013 breakage < http://lab.llvm.org:8011/builders/sanitizer-windows/builds/26666/steps/run%20tests/logs/stdio> which results us having to alter LLVM. While we have no documented policy of supporting two version of MSVC, we do have an informal agreement that we should support the last two versions. I suggest that we alter our informal policy to the following:

(re-sending to the actual mailing lists... go go gadget typos!) On Sun, Oct 27, 2013 at 2:23 AM, Chandler Carruth <chandlerc at google.com>wrote: > Greetings, > > This has been discussed many times, and there are a lot of pro's and con's > on each side, but increasingly I think the project needs to draw a line in > the sand and put in place long-term policies around