From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Chris Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/2] warn on implicit type
Date: Thu, 8 Jun 2017 04:47:34 +0200 [thread overview]
Message-ID: <20170608024736.49780-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this mini-series is to warn about implicit.
It's part of a larger series whose goal is to straighten
situations where the return type of a function doesn't
match the type of what is returned, often silently and
with incoherence in the code generated.
This series can also be pulled from:
git://github.com/lucvoo/sparse.git implicit-int
----------------------------------------------------------------
Luc Van Oostenryck (2):
ret-void: add test case for toplevel asm
ret-void: warn for implicit type
parse.c | 9 +++++++++
validation/alias-mixed.c | 2 +-
validation/asm-toplevel.c | 7 +++++++
validation/badtype2.c | 1 +
validation/implicit-ret-type.c | 15 +++++++++++++++
validation/implicit-type.c | 14 ++++++++++++++
validation/typedef_shadow.c | 1 +
7 files changed, 48 insertions(+), 1 deletion(-)
create mode 100644 validation/asm-toplevel.c
create mode 100644 validation/implicit-ret-type.c
create mode 100644 validation/implicit-type.c
next reply other threads:[~2017-06-08 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 2:47 Luc Van Oostenryck [this message]
2017-06-08 2:47 ` [PATCH 1/2] ret-void: add test case for toplevel asm Luc Van Oostenryck
2017-06-08 2:47 ` [PATCH 2/2] ret-void: warn for implicit type Luc Van Oostenryck
2017-06-08 6:16 ` [PATCH 0/2] warn on " Christopher Li
2017-06-08 7:25 ` 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=20170608024736.49780-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 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).