Making GCC and other C++ compilers very strict

Question

I'm working on a large collaborative C++ project that is both developed and run on various flavors of Linux, OS X and Windows. We compile across these platforms with GCC, Visual Studio C++ and the Intel C++ compiler. As more and more people start developing code for the project, we're starting to see weird errors in compilation and runtime that are specific to particular compilers on particular operating systems. An example of this is implicit inclusion of headers that certain OS/compiler pairs seem to find for you, accidentally overloading a function from a base class in a derived class.

My goal is to make compilation on GCC more strict and catch more errors across all platforms so that we don't keep running into these problems. Here's my list of flags that I'm thinking about trying out for GCC that I've found via Google and the GCC man pages:

• -Wall
• -Wextra
• -Winit-self
• -Wold-style-cast
• -Woverloaded-virtual
• -Wuninitialized
• -Wmissing-declarations
• -Winit-self
• -ansi
• -pedantic

What are the other flags that people use to make GCC (and less importantly Visual Studio C++ and the Intel C++ Compiler) obey a stricter standard of the C++ language? Be specific about which compiler and version you're talking about, as some of these might not be implemented in all versions of all compilers.

Answer 1

Beside the pedantic-error that everyone else suggested, IMO, it's always good to run lint as part of your compile process.

There are some tools out there:

• cpplint (free)
• gimple lint
• coverity

They will save a lot of your time.

Answer 2

You can make pedantic warnings into errors with -pedantic-errors. This will prevent developers from ignoring it. For that matter you could make all warnings into errors as well with -Werror although that can be counter productive in some cases (maybe not in yours though).

Overall, I think, as far as adhering to a strict standard goes, the -pedantic options are the most helpful.

Answer 3

Copy and paste the below line into your master CMake file. The below line comprises almost most useful compiler flags in order to test yourself stricter.

set(CMAKE_CXX_FLAGS "-O0 -fno-elide-constructors -pedantic-errors -ansi -Wextra -Wall     -Winit-self -Wold-style-cast -Woverloaded-virtual -Wuninitialized -Wmissing-declarations    -Winit-self -std=c++98")

If you don’t use CMake, just copy the flags in double quotes and send them to your compiler.

Answer 4

-pedantic-errors.

See more on gcc(1).