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

[Patrik Hägglund H]

We have our own out-of tree LLVM backend (and our own front-end) and continuously track svn trunk (automatic merge or associated tests fails - and need manual intervention - about one or a few times per week). Our code don't have any problem with 'configure --enable-cxx11' right now, and I expect a change to C++11 to be a quite small problem for us, compared to all other problems we face when tracking svn trunk. At least, if I'm wrong and the churn turns out be large, I expect each problem will be relatively easy to fix (compared to other problems, which occasionally take up to a week to fix).

/Patrik Hägglund

-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of dag at cray.com
Sent: den 5 november 2013 19:01
To: clang-dev Developers; LLVM Developers Mailing List
Subject: Re: [LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers

Richard Smith <richard at metafoo.co.uk> writes:

>     I'm objecting to 1 month for svn trunk - 2 months notice is even
>     pushing it imho.
>     
>     1) This is imho not the small change which it's being presented as
>     2) As someone else stated - there are projects tracking svn trunk
>     and telling them to just stop doing that and follow the previous
>     release is untenable without sufficient notice. (It just doesn't
>     seem fair)
>
> If such projects exist and don't want to switch to C++11 mode, I think
> we should let them speak up, and not delay our own plans on the
> hypothesis that they exist. (Maybe they'll say that this is sufficient
> notice, maybe not, but we can't really guess.)

I'm not objecting to C++11 at all.  I would love it!  But I do agree
that 1-2 months notice for a toolchain update on trunk is too short.
I've been hammered countless times about not working off trunk and I am
moving us in the direction of working off trunk (or at least something
close to it).  Short-notice toolchain changes on trunk are going to
hamper that effort.

It is a massive undertaking to test all of our compiler-related software
once we change the toolchain used to build it.  If there is consensus on
which toolchain to move to about 4-6 months out, that seems like
sufficient time to do testing.  This means that for the next release, a
decision on toolchain needs to be made pretty soon after cutting the
previous release.

                            -David
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev