On 31 Mar 2018, at 14:25, Antoine Brodin <anto...@freebsd.org> wrote:
> 
> On Sat, Mar 31, 2018 at 11:38 AM, Dimitry Andric <d...@freebsd.org> wrote:
>> Author: dim
>> Date: Sat Mar 31 11:38:16 2018
>> New Revision: 331838
>> URL: https://svnweb.freebsd.org/changeset/base/331838
>> 
>> Log:
>>  Merge clang, llvm, lld, lldb, compiler-rt and libc++ 6.0.0 release, and
>>  several follow-up fixes.
> ...
> Index: CompilerInvocation.cpp
> ===================================================================
> --- CompilerInvocation.cpp      (revision 331837)
> +++ CompilerInvocation.cpp      (revision 331838)
> ...
> @@ -1690,11 +1765,7 @@
>       break;
>     case InputKind::CXX:
>     case InputKind::ObjCXX:
> -      // The PS4 uses C++11 as the default C++ standard.
> -      if (T.isPS4())
> -        LangStd = LangStandard::lang_gnucxx11;
> -      else
> -        LangStd = LangStandard::lang_gnucxx98;
> +      LangStd = LangStandard::lang_gnucxx14;
>       break;
>     case InputKind::RenderScript:
>       LangStd = LangStandard::lang_c99;
> ...
> 
> Hi,
> 
> Is it safe to change the default c++ standard from gnu++98 to gnu++14
> in a stable branch?
> Around 380 ports are still broken by the gnu++98 -> gnu++14 switch.

It's an upstream choice, which also corresponds to what gcc 6 and higher
have been doing for a longer time.  It's been almost 3 months now since
clang 6 landed in head, and if those ports require USE_CXXSTD=gnu++98 to
be fixed, why haven't those already been changed already?

That said, I'll be happy to go over the list and push in patches, if it
is simply to due to lack of maintainer time.

-Dimitry

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to