[cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers

[Chandler Carruth]

On Mon, Oct 28, 2013 at 2:18 AM, David Tweed <david.tweed at gmail.com> wrote:

> 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 release time. On Update 1 they added
>> support for building Windows XP applications with the VS 2012 compiler.
>>
>> VS 2013 C++ compiler can build XP applications too.
>>
>
> So this complexity highlights to me one important thing: whatever group of
> MSVC tools are
> selected as the baseline, it would be really helpful to have people
> knowledgeable
> about that contribute to the description of precisely which C++11
> constructs are
> allowed (and if there are any surprising cases which don't work), for
> those of us
> who have no idea precisely what will get past an MSVC compiler and no means
> or desire to set up a Windows system just for testing. It's very
> frustrating when
> development turns in to a "I checked on all my systems, checked in and get
> complaints from people on very different systems whose build broke"
> experience.
> (Yeah, I know there's any irony there...) Getting a clearly delimited
> feature list
> should help reduce that.
>

Fortunately, we have a bunch of really active contributors working closely
with Visual Studio. =] I'm very confident that between Reid, Warren, Hans,
Rui, Michael, Anton, and others we can figure out clear and well understood
guidelines.

Naturally, building with Visual Studio will be the final test. We have
build bots and a lot of active developers so I don't think we'll lose sight
of this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20131028/d7cdd30d/attachment.html>