public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: behanw@converseincode.com
Cc: mmarek@suse.cz, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, dl9pf@gmx.de, pageexec@freemail.hu,
	mcharleb@gmail.com
Subject: Re: [PATCH] kbuild, LLVMLinux: only use warnings when using clang
Date: Tue, 1 Jul 2014 12:12:14 +0200	[thread overview]
Message-ID: <20140701101214.GA14882@pd.tnic> (raw)
In-Reply-To: <1404175346-12330-1-git-send-email-behanw@converseincode.com>

On Mon, Jun 30, 2014 at 05:42:26PM -0700, behanw@converseincode.com wrote:
> From: Behan Webster <behanw@converseincode.com>
> 
> Only consider clang warnings in Kbuild when using the clang compiler.
> 
> Signed-off-by: Behan Webster <behanw@converseincode.com>
> ---
>  scripts/Makefile.extrawarn | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/scripts/Makefile.extrawarn b/scripts/Makefile.extrawarn
> index 6564350..e350127 100644
> --- a/scripts/Makefile.extrawarn
> +++ b/scripts/Makefile.extrawarn
> @@ -26,7 +26,7 @@ warning-1 += $(call cc-option, -Wmissing-include-dirs)
>  warning-1 += $(call cc-option, -Wunused-but-set-variable)
>  warning-1 += $(call cc-disable-warning, missing-field-initializers)
>  
> -# Clang
> +ifeq ($(COMPILER),clang)
>  warning-1 += $(call cc-disable-warning, initializer-overrides)
>  warning-1 += $(call cc-disable-warning, unused-value)
>  warning-1 += $(call cc-disable-warning, format)
> @@ -35,6 +35,7 @@ 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)
> +endif

Ok, just to make sure I understand that whole use case correctly:

The disabling of those warnings is really intended for the case where
people build the kernel with "W=1" on the make cmdline *and* clang?

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-07-01 10:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 13:07 3d3d6b847420 ("kbuild: LLVMLinux: Adapt warnings for compilation with clang") Borislav Petkov
2014-06-16 15:29 ` PaX Team
2014-06-16 15:48   ` Jan-Simon Möller
2014-06-29 20:13     ` Borislav Petkov
2014-07-01  0:42       ` [PATCH] kbuild, LLVMLinux: only use warnings when using clang behanw
2014-07-01 10:12         ` Borislav Petkov [this message]
2014-07-30 13:04           ` Michal Marek
2014-07-30 21:39             ` Behan Webster
2014-07-31  4:16             ` [PATCH v2] kbuild, LLVMLinux: Supress warnings unless W=1-3 behanw
2014-07-31  8:18               ` Michal Marek
2014-07-31 16:12                 ` Behan Webster
2014-07-31 20:46                   ` Michal Marek
2014-08-01  4:07                     ` Behan Webster
2014-08-01  4:08                     ` [PATCH v3] " behanw
2014-08-05 13:42                       ` Michal Marek

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=20140701101214.GA14882@pd.tnic \
    --to=bp@alien8.de \
    --cc=behanw@converseincode.com \
    --cc=dl9pf@gmx.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcharleb@gmail.com \
    --cc=mmarek@suse.cz \
    --cc=pageexec@freemail.hu \
    /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