From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/8] avoid duplicated warnings
Date: Fri, 2 Feb 2018 13:17:27 +0100 [thread overview]
Message-ID: <20180202121735.39621-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this series is to eliminate some duplicated
warnings in order to reduce noise and allow to better
focus on the origin of the problem.
The series is also available in the Git repository at:
git://github.com/lucvoo/sparse-dev.git expr-bad-twice
----------------------------------------------------------------
Luc Van Oostenryck (8):
add testcases for duplicated warning about invalid types
fix error in bad conditional
early return if null ctype in evaluate_conditional()
add helper: valid_type()
use valid_type to avoid to warn twice on conditionals
add helpers: valid_expr_type() & valid_subexpr_type()
do not report bad types twice
always evaluate both operands
evaluate.c | 66 +++++++++++++++++++++++++++-----------------
symbol.h | 5 ++++
validation/bad-type-twice0.c | 13 +++++++++
validation/bad-type-twice1.c | 16 +++++++++++
validation/bad-type-twice2.c | 18 ++++++++++++
5 files changed, 93 insertions(+), 25 deletions(-)
create mode 100644 validation/bad-type-twice0.c
create mode 100644 validation/bad-type-twice1.c
create mode 100644 validation/bad-type-twice2.c
--
2.16.0
next reply other threads:[~2018-02-02 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 12:17 Luc Van Oostenryck [this message]
2018-02-02 12:17 ` [PATCH 1/8] add testcases for duplicated warning about invalid types Luc Van Oostenryck
2018-02-02 12:17 ` [PATCH 2/8] fix error in bad conditional Luc Van Oostenryck
2018-02-02 12:17 ` [PATCH 3/8] early return if null ctype in evaluate_conditional() Luc Van Oostenryck
2018-02-10 19:28 ` Christopher Li
2018-02-10 19:43 ` Luc Van Oostenryck
2018-02-02 12:17 ` [PATCH 4/8] add helper: valid_type() Luc Van Oostenryck
2018-02-10 19:38 ` Christopher Li
2018-02-10 19:51 ` Luc Van Oostenryck
2018-02-02 12:17 ` [PATCH 5/8] use valid_type to avoid to warn twice on conditionals Luc Van Oostenryck
2018-02-02 12:17 ` [PATCH 6/8] add helpers: valid_expr_type() & valid_subexpr_type() Luc Van Oostenryck
2018-02-02 12:17 ` [PATCH 7/8] do not report bad types twice Luc Van Oostenryck
2018-02-02 12:17 ` [PATCH 8/8] always evaluate both operands 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=20180202121735.39621-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.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