894242 - Make C++0x/C++11 mode of gcc/clang mandatory

Status: RESOLVED FIXED

(Firefox Build System :: General, defect)

Comment 1

[Mike Hommey [:glandium]]

Attachment: Make C++0x/C++11 mode of gcc/clang mandatory

Comment 2

[(not currently active) Ted Mielczarek]

Comment on attachment 776214 [details] [diff] [review]
Make C++0x/C++11 mode of gcc/clang mandatory

Review of attachment 776214 [details] [diff] [review]:
-----------------------------------------------------------------

We're probably going to need something to catch other compilers that don't properly support C++0x features we want to use, aren't we?

Comment 3

[Mike Hommey [:glandium]]

(In reply to Ted Mielczarek [:ted.mielczarek] from comment #2)
> We're probably going to need something to catch other compilers that don't
> properly support C++0x features we want to use, aren't we?

You mean sun studio and others?

Comment 4

[Reece H. Dunn]

NOTE: I have a set of C++11 autoconf checks available at https://github.com/rhdunn/cainteoir-engine/blob/master/m4/cxx11.m4:

CXX11_CHECK_CXX11_SUPPORT -- checks what flags (if any) are needed for C++11 (double right-angle bracket support only)

CXX11_NULLPTR -- requires C++11 nullptr support
CXX11_DECLTYPE -- requires C++11 decltype support
CXX11_AUTO -- requires C++11 auto support
CXX11_RANGE_BASED_FOR -- requires C++11 range-based for support
CXX11_BRACE_INITIALIZATION -- requires C++11 brace initialization support (with a check for clang bug 12670)
CXX11_SCOPED_ENUMS -- requires C++11 scoped enums (i.e. 'enum class') support
CXX11_CONSTEXPR -- requires C++11 constexpr support
CXX11_LAMBDA -- requires basic C++11 lambda support
CXX11_LAMBDA_CAPTURE -- requires C++11 lambda capture syntax support

CXX11_HAVE_STD_INITIALIZER_LIST -- set HAVE_CXX11_STD_INITIALIZER_LIST if std::initializer_list is supported
CXX11_REQUIRE_STD_INITIALIZER_LIST -- error if std::initializer_list is not supported

CXX11_HAVE_STD_SHARED_PTR -- set HAVE_CXX11_STD_SHARED_PTR if std::shared_ptr is supported
CXX11_REQUIRE_STD_SHARED_PTR -- error if std::shared_ptr is not supported

CXX11_HAVE_STD_BEGIN -- set HAVE_CXX11_STD_BEGIN if std::begin is supported
CXX11_REQUIRE_STD_BEGIN -- error if std::begin is not supported

CXX11_HAVE_STD_END -- set HAVE_CXX11_STD_END if std::end is supported
CXX11_REQUIRE_STD_END -- error if std::end is not supported

I can move this out to a separate project on GitHub and add more C++11 (and C++1y features -- like std::make_unique) as needed. I can also support HAVE vs REQUIRE macros for the language features, if needed.

Comment 5

[(not currently active) Ted Mielczarek]

(In reply to Mike Hommey [:glandium] from comment #3)
> (In reply to Ted Mielczarek [:ted.mielczarek] from comment #2)
> > We're probably going to need something to catch other compilers that don't
> > properly support C++0x features we want to use, aren't we?
> 
> You mean sun studio and others?

Yes. AFAIK we haven't unsupported building with non-GCC/clang, but I'm fine with requiring C++11 features even if that means unsupporting them as a side effect.

Comment 6

[Mike Hommey [:glandium]]

(In reply to Reece H. Dunn from comment #4)
> NOTE: I have a set of C++11 autoconf checks available at
> https://github.com/rhdunn/cainteoir-engine/blob/master/m4/cxx11.m4:

Testing implementation bugs might be a good thing, but testing the features we're going to use (we're not going to conditionally use them), besides the fact that it will make the build error out at configure time instead of build time, I'm not sure it's worth bothering.

Comment 7

[Joshua Cranmer [:jcranmer]]

(In reply to Mike Hommey [:glandium] from comment #6)
> (In reply to Reece H. Dunn from comment #4)
> > NOTE: I have a set of C++11 autoconf checks available at
> > https://github.com/rhdunn/cainteoir-engine/blob/master/m4/cxx11.m4:
> 
> Testing implementation bugs might be a good thing, but testing the features
> we're going to use (we're not going to conditionally use them), besides the
> fact that it will make the build error out at configure time instead of
> build time, I'm not sure it's worth bothering.

If we can error for clean, obvious reasons in the build early on, then a configure check strikes me as superfluous. I'm biased towards trying to do as little in configure as possible.

Comment 8

[Mike Hommey [:glandium]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/5939320824b1

Comment 9

[Carsten Book [:Tomcat]]

backout https://hg.mozilla.org/integration/mozilla-inbound/rev/7e6eb43139f1

Comment 10

[Mike Hommey [:glandium]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/1d17f497c474

Comment 11

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/1d17f497c474

Comment 12

[Ed Morley [:emorley]]

https://hg.mozilla.org/mozilla-central/rev/dc014201581d