From: Dave Jones <davej@redhat.com>
To: behanw@converseincode.com
Cc: mmarek@suse.cz, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, sparse@chrisli.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sparse@vger.kernel.org, torvalds@linux-foundation.org,
dwmw2@infradead.org, pageexec@freemail.hu,
"Jan-Simon Möller" <dl9pf@gmx.de>,
"Mark Charlebois" <mcharleb@gmail.com>
Subject: Re: [PATCH 2/5] kbuild: LLVMLinux: Adapt warnings for compilation with clang
Date: Tue, 25 Feb 2014 20:17:37 -0500 [thread overview]
Message-ID: <20140226011737.GA4564@redhat.com> (raw)
In-Reply-To: <1393376923-21892-3-git-send-email-behanw@converseincode.com>
On Tue, Feb 25, 2014 at 05:08:40PM -0800, behanw@converseincode.com wrote:
> When compiling kernel with clang, disable warnings which are too noisy, and
> add the clang flag catch-undefined-behavior.
>
> +# Clang
> +warning-1 += $(call cc-disable-warning, initializer-overrides)
> +warning-1 += $(call cc-disable-warning, unused-value)
> +warning-1 += $(call cc-disable-warning, format)
> +warning-1 += $(call cc-disable-warning, unknown-warning-option)
> +warning-1 += $(call cc-disable-warning, self-assign)
> +warning-1 += $(call cc-disable-warning, sign-compare)
> +warning-1 += $(call cc-disable-warning, format-zero-length)
> +warning-1 += $(call cc-disable-warning, uninitialized)
> +warning-1 += $(call cc-option, -fcatch-undefined-behavior)
Do you have a pointer to an example log-file from before this change ?
I'm curious for eg, which self-assign warnings are showing up,
because I've been fixing up the ones that Coverity found, of which
there are only a dozen or so left iirc.
Some of the others may also be interesting.
Dave
next prev parent reply other threads:[~2014-02-26 1:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 1:08 [PATCH 0/5] kbuild: LLVMLinux: Initial updates to kbuild to enable the kernel to be compiled with clang/LLVM behanw
2014-02-26 1:08 ` behanw
2014-02-26 1:08 ` [PATCH 1/5] kbuild: LLVMLinux: Add Kbuild support for building kernel with Clang behanw
2014-02-26 1:08 ` behanw
2014-03-09 21:58 ` Sam Ravnborg
2014-03-09 21:58 ` Sam Ravnborg
2014-03-11 6:58 ` Behan Webster
2014-03-11 6:58 ` Behan Webster
2014-03-11 21:26 ` [PATCH 1/5 v2] " behanw
2014-02-26 1:08 ` [PATCH 2/5] kbuild: LLVMLinux: Adapt warnings for compilation with clang behanw
2014-02-26 1:08 ` behanw
2014-02-26 1:17 ` Dave Jones [this message]
2014-02-26 1:31 ` Behan Webster
2014-02-26 1:34 ` H. Peter Anvin
2014-02-26 2:38 ` Behan Webster
2014-03-06 17:59 ` [PATCH 2/5 v2] " behanw
2014-02-26 1:08 ` [PATCH 3/5] kbuild: LLVMLinux: Fix LINUX_COMPILER definition script " behanw
2014-02-26 1:08 ` behanw
2014-02-26 1:08 ` [PATCH 4/5] LLVMLinux: Add support for clang to compiler.h and new compiler-clang.h behanw
2014-02-26 1:08 ` [PATCH 5/5] x86 kbuild: LLVMLinux: More cc-options added for clang behanw
2014-02-26 1:32 ` H. Peter Anvin
2014-02-26 1:44 ` Behan Webster
2014-03-06 18:03 ` [PATCH 5/5 v2] " behanw
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=20140226011737.GA4564@redhat.com \
--to=davej@redhat.com \
--cc=behanw@converseincode.com \
--cc=dl9pf@gmx.de \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mcharleb@gmail.com \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=pageexec@freemail.hu \
--cc=sparse@chrisli.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.