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

[Hinton, Don]

Is the plan to have autoconf and cmake check for the appropriate C++11 features and fail if the chosen compiler doesn't support them?  Or do we just have to wait for some obscure error during the build process some time later?

If autoconf and cmake do the feature checks - they could also tell the user which was the last safe pre-C++11 revision they should go back to.  Also, based on what I've read, it seems that even non-conforming compilers might still support a subset of C++11 features, so a scheduled rollout of new features could make it a little less painful for some users.

Btw, as long as I can build with either an old version of clang or a recent version of gcc (linux), I have no problems going to C++11 or beyond.

thanks...
don

From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Renato Golin
Sent: Friday, November 08, 2013 11:51 AM
To: Richard Smith
Cc: David Greene; 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

On 8 November 2013 11:29, Richard Smith <richard at metafoo.co.uk<mailto:richard at metafoo.co.uk>> wrote:
So I don't see that waiting is a significant win. Conversely, it gives us less time to get the C++11-enabled code tested across relevant toolchains (including perhaps rolling back the change if we find a fatal issue) before we release 3.5 next year.

That's a good point. Still, I think waiting a month for introducing new C++11 code wouldn't hurt either.

I'm guessing people reading this thread have already accepted that we're moving, so they should have be doing all the work to move since last week, which gives us a nice round December frame for new stuff.

David, is that a comfortable window?

cheers,
--renato

This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute, alter or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmissions cannot be guaranteed to be secure or without error as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise during or as a result of e-mail transmission. If verification is required, please request a hard-copy version. This message is provided for information purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments in any jurisdiction.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131108/0f262369/attachment.html>