public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sodagudi Prasad <psodagud@codeaurora.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Michal Marek <mmarek@suse.com>,
	Greg Hackmann <ghackmann@google.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: unused-variable warning is getting disabled with clang
Date: Wed, 06 Dec 2017 13:24:51 -0800	[thread overview]
Message-ID: <56cef2a644acc458b9457e3147abc4c0@codeaurora.org> (raw)


Hi All,

When kernel compiled with clang, following line is disabling the 
unused-variable warning. This is not the case with gcc.
KBUILD_CFLAGS += $(call cc-disable-warning, unused-variable)

Are there any specific reasons for disabling unused-variable with clang?

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
Forum,
Linux Foundation Collaborative Project

             reply	other threads:[~2017-12-06 21:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 21:24 Sodagudi Prasad [this message]
2017-12-07  6:26 ` unused-variable warning is getting disabled with clang Greg Kroah-Hartman
2017-12-08  2:16   ` Sodagudi Prasad
2017-12-18 15:32     ` Masahiro Yamada
2018-01-27  0:59       ` [PATCH] kbuild: clang: Disable -Wunused-const-variable warnings Prasad Sodagudi
2018-01-28 16:22         ` Segher Boessenkool
2018-01-29 16:35           ` Sodagudi Prasad
2018-01-29 17:08             ` Prasad Sodagudi
2018-01-29 23:57               ` Segher Boessenkool
2018-02-02 16:01               ` Masahiro Yamada
2018-02-06 23:46                 ` [PATCH] kbuild: clang: disable unused variable warnings only when constant Prasad Sodagudi
2018-02-07  0:22                   ` Masahiro Yamada

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=56cef2a644acc458b9457e3147abc4c0@codeaurora.org \
    --to=psodagud@codeaurora.org \
    --cc=ghackmann@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=yamada.masahiro@socionext.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox