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

[dag at cray.com]

Renato Golin <renato.golin at linaro.org> writes:

> In a nutshell, if we want the toolchain to evolve with time, we'll
> need to have API changes, and we'll need to update surrounding
> software to cope with that. The only difference is if we want to be
> doing this as our day-to-day job, or twice a year (or even less than
> that if you stay on a release for a while longer). I personally think
> that it's more manageable to do that on releases than on trunk (been
> there, done that, and it sucks).

Except that the core developers recommend working off trunk.  If you
want to contribute code back, you pretty much have to work off trunk.
It is a major pain to port your changes against release x.y forward to
trunk for review and commit.

I want to re-stress that toolchain changes are fine.  We just need
enough notice before they're required on ToT.  I would like to see a
three month notice at the very least.  Four would be better.  We can't
just drop everything we're doing to go test a new toolchain.  We have to
schedule it.

                          -David