From: Alex Dowad <alexinbeijing@gmail.com>
To: musl@lists.openwall.com
Subject: Re: More on warning cleanup
Date: Thu, 28 May 2015 08:55:24 +0200 [thread overview]
Message-ID: <5566BBDC.5080805@gmail.com> (raw)
In-Reply-To: <20150528050853.GA8590@brightrain.aerifal.cx>
On 28/05/15 07:08, Rich Felker wrote:
> Since compilers differ in what warnings they include in -Wall, I'd
> like to remove -Wall (followed by a bunch of -Wno-*) from musl's
> --enable-warnings and instead individually turn on the warnings we
> want. A few weeks ago I worked those out on #musl (based on the GCC
> manual's documentation of -Wall and other options) and here's what I
> came up with:
>
> -Waddress
> -Warray-bounds
> -Wchar-subscripts
> -Wreturn-type
> -Wsequence-point
> -Wstrict-aliasing
> -Wstrict-overflow
> -Wunused-function
> -Wunused-variable
> -Wunused-label
>
> This list does not include the ones we already have as errors because
> they only trigger on invalid C:
>
> -Werror=implicit-function-declaration
> -Werror=implicit-int
> -Werror=pointer-sign
> -Werror=pointer-arith
>
> Are these any other warnings we should enable?
Are you interested in warnings provided by clang, but not by gcc? I've
noticed that there are a few things in musl which clang warns about, but
gcc doesn't; such as expressions where operator precedence might be
confusing to some, and indexing into strings using + (it wants you to
use [] instead).
next prev parent reply other threads:[~2015-05-28 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 5:08 Rich Felker
2015-05-28 6:55 ` Alex Dowad [this message]
2015-05-28 7:29 ` Rich Felker
2015-05-28 13:57 ` Shiz
2015-05-28 17:18 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5566BBDC.5080805@gmail.com \
--to=alexinbeijing@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).