From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Josh Triplett <josh@joshtriplett.org>,
Lance Richardson <lrichard@redhat.com>,
Ramsay Jones <ramsay@ramsayjones.plus.com>,
Randy Dunlap <rdunlap@infradead.org>,
Rui Teng <rui.teng@linux.vnet.ibm.com>,
Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [RFC PATCH 1/2] By default disable the warning flag '-Wunknown-attribute'
Date: Wed, 14 Feb 2018 00:21:08 +0100 [thread overview]
Message-ID: <20180213232109.20933-2-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20180213232109.20933-1-luc.vanoostenryck@gmail.com>
Generally, we're not interested by those warnings, but we
can always explicitly ask for them if needed.
So make the flag '-Wunknown-attribute' off by default.
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 fcd31e84c..aec52a6fa 100644
--- a/lib.c
+++ b/lib.c
@@ -251,7 +251,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 dump_macro_defs = 0;
diff --git a/validation/Wunknown-attribute-def.c b/validation/Wunknown-attribute-def.c
index 0c0868d6b..defe643db 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.16.0
next prev parent reply other threads:[~2018-02-13 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 23:21 [RFC PATCH 0/2] drop the concept of 'known-but-ignored' attributes Luc Van Oostenryck
2018-02-13 23:21 ` Luc Van Oostenryck [this message]
2018-02-13 23:21 ` [RFC PATCH 2/2] " Luc Van Oostenryck
2018-02-15 15:57 ` [RFC PATCH 0/2] " Josh Triplett
2018-02-15 17:33 ` Linus Torvalds
2018-02-15 17:54 ` Josh Triplett
2018-02-15 20:03 ` Luc Van Oostenryck
2018-02-15 19:53 ` Luc Van Oostenryck
2018-02-15 20:06 ` Christopher Li
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=20180213232109.20933-2-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=lrichard@redhat.com \
--cc=ramsay@ramsayjones.plus.com \
--cc=rdunlap@infradead.org \
--cc=rui.teng@linux.vnet.ibm.com \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.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).