This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Should -Wmaybe-uninitialized be included in -Wall?
- From: Jed Davis <jld at mozilla dot com>
- To: Andi Kleen <andi at firstfloor dot org>
- Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, Andrew Haley <aph at redhat dot com>, Andreas Arnez <arnez at linux dot vnet dot ibm dot com>, gcc at gcc dot gnu dot org
- Date: Fri, 12 Jul 2013 12:40:02 -0700
- Subject: Re: Should -Wmaybe-uninitialized be included in -Wall?
- References: <87ehb8rljz dot fsf at br87z6lw dot de dot ibm dot com> <51DBFC32 dot 8050401 at redhat dot com> <8761wiiihc dot fsf at tassilo dot jf dot intel dot com> <CAAiZkiBcJW0OH8dtkhUCvhrkHiKt4S3xAgurEdqTJskU3mdjHA at mail dot gmail dot com> <20130710161111 dot GY6123 at two dot firstfloor dot org>
On Wed, Jul 10, 2013 at 06:11:11PM +0200, Andi Kleen wrote:
> FWIW basically -Werror -Wall defines a compiler version specific
> variant of C. May be great for individual developers, but it's always
> a serious mistake in any distributed Makefile.
Not always. Any project large enough (or serious enough about build
reproducibility) to include its own toolchain can be written in that
compiler-version-specific subset and nonetheless be worked on by more
than one person. This is not uncommon in the BSDs, for example; see
instances of "WARNS=4".
It's an uncommon use case (and, I think, not a justification for changing
-Wall), but it does exist and it is useful.
--Jed