dag at cray.com
2013-Nov-07 17:04 UTC
[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
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
Chandler Carruth
2013-Nov-07 17:59 UTC
[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
On Thu, Nov 7, 2013 at 9:04 AM, <dag at cray.com> wrote:> 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. >The need to base your work off of trunk to contribute it back is an inherent fact of life with a project that moves as fast as LLVM. No amount of stable APIs would remove this pressure. This does (naturally) come with a cost. Chasing API changes is easily the most impactful thing we deal with here, and I suspect it is for others as well. It still is less expensive (IMO) than doing one-off updates from release X to release X+N. And it still dwarfs the cost of using a reasonably modern toolchain. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131107/d9dff7e0/attachment.html>
Renato Golin
2013-Nov-08 06:49 UTC
[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
On 7 November 2013 09:59, Chandler Carruth <chandlerc at google.com> wrote:> The need to base your work off of trunk to contribute it back is an > inherent fact of life with a project that moves as fast as LLVM. >Well, actually, on *any* open source project. Not all side-projects *want* to contribute back, and that was one of my concerns, but it seems not to be the problem, so I remove my observation from the pool. --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131107/6cc25a2c/attachment.html>
Maybe Matching Threads
- [LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
- [LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
- [LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
- [LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
- [LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers