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 0/3] reduce noise from unknown attributes
Date: Wed, 2 Nov 2016 22:59:36 +0100 [thread overview]
Message-ID: <20161102215939.36765-1-luc.vanoostenryck@gmail.com> (raw)
Currently sparse throws error each time at each unknown attributes.
As GCC often creates new attributes, generaly for specific
usages irrelevant to what sparse is used for. The errors from
these not-yet-known attributes create needless noise and annoyance
for no benefits.
This series aims at reduce this noise by doing 3 things:
* change the error to a warning
* add a new flag to disable or enable warnings from those attributes
* by default set this flag as disabled
The first patch is independent of the others two.
Luc Van Oostenryck (3):
Warn on unknown attributes instead of throwing errors
Add a new warning flag: '-Wunknown-attribute'
By default disable the new warning flag '-Wunknown-attribute'
lib.c | 2 ++
lib.h | 1 +
parse.c | 3 ++-
validation/Wunknown-attribute-def.c | 8 ++++++++
validation/Wunknown-attribute-no.c | 9 +++++++++
validation/Wunknown-attribute-yes.c | 10 ++++++++++
6 files changed, 32 insertions(+), 1 deletion(-)
create mode 100644 validation/Wunknown-attribute-def.c
create mode 100644 validation/Wunknown-attribute-no.c
create mode 100644 validation/Wunknown-attribute-yes.c
--
2.10.1
next reply other threads:[~2016-11-02 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 21:59 Luc Van Oostenryck [this message]
2016-11-02 21:59 ` [PATCH 1/3] Warn on unknown attributes instead of throwing errors Luc Van Oostenryck
2016-11-02 22:29 ` Ramsay Jones
2016-11-02 23:09 ` Luc Van Oostenryck
2016-11-02 21:59 ` [PATCH 2/3] Add a new warning flag: '-Wunknown-attribute' Luc Van Oostenryck
2016-11-02 21:59 ` [PATCH 3/3] By default disable '-Wunknown-attribute' Luc Van Oostenryck
2016-11-17 16:52 ` Christopher Li
2016-11-17 18:04 ` 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=20161102215939.36765-1-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.