- To: noloader@xxxxxxxxx
- Subject: Re: GCC warning options for numerical programs
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Date: Mon, 23 Apr 2012 19:15:07 +0100
- Cc: Andrew Haley <aph@xxxxxxxxxx>, gcc-help@xxxxxxxxxxx
- Comment: DKIM? See http://www.dkim.org
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- In-reply-to: <CAH8yC8nNgbg8kq77Die9eemMDXmkeu=D6mX9EoFj+atXe_1CUQ@mail.gmail.com>
On 23 April 2012 16:26, Jeffrey Walton wrote:
>
> What worries me is missing a detail and later getting pwn'd. Consider
> how many times Dan Rosenberg has dinged the l33t k3rn3l hack3rz for
> CompSci 101 stuff such as not validating parameters or using
> uninitialized variables. GCC will warn for some of these CompSci 101
> transgressions.
How many of them are *not* covered by -Wall -Wextra?
If there are GCC warnings not included by -Wall -Wextra that would
have helped avoid those problems then you might have a point. If the
warnings are already enabled by one of those options then -Weverything
won't help. Hitting programmers with a cluebat for not using -Wall
would be more effective.
> Additionally, the kernel's random.c and prng.c violate
> GCC's aliasing rules. I believe GCC warns of aliasing and punning
> (correct me here), but the kernel folks are too l33t to use GCC's
> static analysis capabilities [1].
How would ading -Weverything change that?
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]