From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: disable -Wmissing-field-initializers for W=1
Date: Tue, 24 Jan 2012 05:10:14 +0200 [thread overview]
Message-ID: <20120124031014.GA12570@otc-wbsnb-06> (raw)
In-Reply-To: <20120123211834.GA3981@sepie.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]
On Mon, Jan 23, 2012 at 10:18:34PM +0100, Michal Marek wrote:
> On Mon, Jan 23, 2012 at 05:54:10AM +0200, Kirill A. Shutemov wrote:
> > -Wmissing-field-initializers is too noisy to be useful on W=1. Let's
> > move it to W=2.
> >
> > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > ---
> > scripts/Makefile.build | 3 ++-
> > 1 files changed, 2 insertions(+), 1 deletions(-)
> >
> > diff --git a/scripts/Makefile.build b/scripts/Makefile.build
> > index d2b366c..1535a2f 100644
> > --- a/scripts/Makefile.build
> > +++ b/scripts/Makefile.build
> > @@ -62,7 +62,7 @@ endif
> > ifdef KBUILD_ENABLE_EXTRA_GCC_CHECKS
> > warning- := $(empty)
> >
> > -warning-1 := -Wextra -Wunused -Wno-unused-parameter
> > +warning-1 := -Wextra -Wunused -Wno-unused-parameter -Wno-missing-field-initializers
>
> I would use $(call cc-disable-warning, missing-field-initializers), so
> that W=1 has a chance of working with gcc 3.x.
Something like this?
---
From 9ee1c7006d14efddcb7cd52053b97aa39edf6ec3 Mon Sep 17 00:00:00 2001
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Date: Mon, 23 Jan 2012 04:59:28 +0200
Subject: [PATCH] kbuild: disable -Wmissing-field-initializers for W=1
-Wmissing-field-initializers is too noisy to be useful on W=1. Let's
move it to W=2.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
---
scripts/Makefile.build | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/scripts/Makefile.build b/scripts/Makefile.build
index d2b366c..ff1720d 100644
--- a/scripts/Makefile.build
+++ b/scripts/Makefile.build
@@ -69,6 +69,7 @@ warning-1 += -Wmissing-prototypes
warning-1 += -Wold-style-definition
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)
warning-2 := -Waggregate-return
warning-2 += -Wcast-align
@@ -76,6 +77,7 @@ warning-2 += -Wdisabled-optimization
warning-2 += -Wnested-externs
warning-2 += -Wshadow
warning-2 += $(call cc-option, -Wlogical-op)
+warning-2 += $(call cc-option, -Wmissing-field-initializers)
warning-3 := -Wbad-function-cast
warning-3 += -Wcast-qual
--
1.7.8.3
--
Kirill A. Shutemov
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-24 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 3:54 Kirill A. Shutemov
2012-01-23 21:18 ` Michal Marek
2012-01-24 3:10 ` Kirill A. Shutemov [this message]
2012-01-26 10:10 ` 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=20120124031014.GA12570@otc-wbsnb-06 \
--to=kirill.shutemov@linux.intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®