From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH v2 3/3] By default disable the new warning flag '-Wunknown-attribute'
Date: Thu, 3 Nov 2016 00:07:39 +0100 [thread overview]
Message-ID: <20161102230739.64519-4-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20161102230739.64519-1-luc.vanoostenryck@gmail.com>
Generally, we won't be interested by those warnings, but we
can always explicitly ask for them if needed.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
lib.c | 2 +-
validation/Wunknown-attribute-def.c | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib.c b/lib.c
index 138736e7..b4b09a78 100644
--- a/lib.c
+++ b/lib.c
@@ -240,7 +240,7 @@ int Wtransparent_union = 0;
int Wtypesign = 0;
int Wundef = 0;
int Wuninitialized = 1;
-int Wunknown_attribute = 1;
+int Wunknown_attribute = 0;
int Wvla = 1;
int dbg_entry = 0;
diff --git a/validation/Wunknown-attribute-def.c b/validation/Wunknown-attribute-def.c
index 0c0868d6..defe643d 100644
--- a/validation/Wunknown-attribute-def.c
+++ b/validation/Wunknown-attribute-def.c
@@ -4,6 +4,5 @@ static int foo(void) __attribute__((unknown_attribute));
* check-name: warn-unknown-attribute
*
* check-error-start
-Wunknown-attribute-def.c:1:37: warning: attribute 'unknown_attribute': unknown attribute
* check-error-end
*/
--
2.10.1
next prev parent reply other threads:[~2016-11-02 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 23:07 [PATCH v2 0/3] reduce noise from unknown attributes Luc Van Oostenryck
2016-11-02 23:07 ` [PATCH v2 1/3] Warn on unknown attributes instead of throwing errors Luc Van Oostenryck
2016-11-02 23:07 ` [PATCH v2 2/3] Add a new warning flag: '-Wunknown-attribute' Luc Van Oostenryck
2016-11-02 23:07 ` Luc Van Oostenryck [this message]
2016-11-17 17:06 ` [PATCH v2 0/3] reduce noise from unknown attributes Christopher Li
2016-11-17 17:34 ` Luc Van Oostenryck
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=20161102230739.64519-4-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).