From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [pull] static analysis, and help to translator
Date: Mon, 16 Jul 2012 17:51:59 +0200 [thread overview]
Message-ID: <20120716155159.GA9087@x2.net.home> (raw)
In-Reply-To: <CAG27Bk0qDyt0q7vVtCeOgdWDN_r7mW+gUVnyMLUjY1CnbT+LZw@mail.gmail.com>
On Sun, Jul 15, 2012 at 10:40:30PM +0200, Sami Kerola wrote:
> build-sys: reduce warning noise when compiling with clang
.. I spent hour to improve UL_WARN_ADD and after commit and push I
found that whole problem could be resolved by an extra -Werror in
UL_WARN_ADD implementation.
so the result from CC=clang ./configure is:
checking whether compiler handles -Wextra... yes
checking whether compiler handles -Wno-missing-field-initializers... yes
checking whether compiler handles -Wsign-compare... yes
checking whether compiler handles -Wtype-limits... yes
checking whether compiler handles -Wuninitialized... yes
checking whether compiler handles -Werror=sequence-point... yes
checking whether compiler handles -Wunused-parameter... yes
checking whether compiler handles -fno-common... yes
checking whether compiler handles -Wunused-result... no
checking whether compiler handles -Wmissing-prototypes... yes
checking whether compiler handles -Wunused-variable... yes
checking whether compiler handles -Wmissing-parameter-type... no
checking whether compiler handles -Wunused-but-set-parameter... no
checking whether compiler handles -Wunused-but-set-variable... no
checking whether compiler handles -Wredundant-decls... yes
> libblkid: remove duplicate entries in symbols
> lib/pager: minor compiler warning fixes
> findmnt: add missing initializer
Why we need this if code is compiled with -Wno-missing-field-initializers?
It's pretty obvious in C standard how are missing fields are initialized
in global and static variables.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-07-16 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 20:40 [pull] static analysis, and help to translator Sami Kerola
2012-07-16 15:51 ` Karel Zak [this message]
2012-07-16 16:27 ` Karel Zak
2012-07-16 17:44 ` Davidlohr Bueso
2012-07-17 6:06 ` Sami Kerola
2012-07-17 10:03 ` Davidlohr Bueso
2012-07-17 12:03 ` Sami Kerola
2012-07-17 12:11 ` Davidlohr Bueso
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=20120716155159.GA9087@x2.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@gmail.com \
--cc=util-linux@vger.kernel.org \
/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.
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).