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
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
