From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: More on warning cleanup
Date: Thu, 28 May 2015 03:29:22 -0400 [thread overview]
Message-ID: <20150528072922.GS17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <5566BBDC.5080805@gmail.com>
On Thu, May 28, 2015 at 08:55:24AM +0200, Alex Dowad wrote:
> >Are these any other warnings we should enable?
> Are you interested in warnings provided by clang, but not by gcc?
Possibly.
> 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).
Only interested in warnings that catch non-portable constructs,
near-certain bugs (e.g. UB if the code is reached), typos (unused
warnings help here), etc.
Not interested in coding style policing, and definitely not interested
in warnings that are intended for JS or Python programmers trying to
write their first C program. :-)
Rich
next prev parent reply other threads:[~2015-05-28 7:29 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
2015-05-28 7:29 ` Rich Felker [this message]
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=20150528072922.GS17573@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).