From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/8] Add Sparse based checker and TST_RET/ERR check
Date: Wed, 14 Jul 2021 12:43:31 +0200 [thread overview]
Message-ID: <YO6/0+gPhMh/mbW7@pevik> (raw)
In-Reply-To: <20210714071158.15868-2-rpalethorpe@suse.com>
Hi Richie,
> Vendors in Sparse as a git module. Then uses it to check for stores to
> TST_RET/ERR within the library.
I think submodules are a bit problematic, thus I'd prefer avoiding them.
But whole thing is integrated nicely, thus:
Reviewed-by: Petr Vorel <pvorel@suse.cz>
...
> diff --git a/tools/sparse/README.md b/tools/sparse/README.md
...
> +# Sparse based linting
> +
> +Note that while it is possible to build Sparse with Clang. This may
> +cause some issues. Namely `GCC_BASE` is set to the Clang resource
> +directory. This contains some headers Sparse can not parse.
> +
> +[1]: Many distributions have a Sparse package. This only contains some executables. There is no shared library
nit: missing dot here.
> diff --git a/tools/sparse/main.c b/tools/sparse/main.c
> new file mode 100644
> index 000000000..58f9a549c
> --- /dev/null
> +++ b/tools/sparse/main.c
> @@ -0,0 +1,148 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) 2021 SUSE LLC <rpalethorpe@suse.com>
> + *
> + * Sparse allows us to perform checks on the AST (struct symbol) or on
> + * a linearized representation. In the latter case we are given a set
> + * of entry points (functions) containing basic blocks of
> + * instructions.
> + *
> + * The basic blocks contain byte code in SSA form. This is similar to
> + * the the intermediate representation most compilers use during
nit: repeated the
> + * optimisation.
> + */
The rest LGTM.
Kind regards,
Petr
next prev parent reply other threads:[~2021-07-14 10:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 7:11 [LTP] [PATCH v2 0/8] Sparse based checker and rule proposal Richard Palethorpe
2021-07-14 7:11 ` [LTP] [PATCH v2 1/8] Add Sparse based checker and TST_RET/ERR check Richard Palethorpe
2021-07-14 10:43 ` Petr Vorel [this message]
2021-07-14 11:21 ` Joerg Vehlow
2021-07-14 13:06 ` Richard Palethorpe
2021-07-19 14:51 ` Cyril Hrubis
2021-07-14 7:11 ` [LTP] [PATCH v2 2/8] Add 'make check' to the build system Richard Palethorpe
2021-07-14 10:46 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 3/8] doc: Add rules and recommendations list Richard Palethorpe
2021-07-14 10:49 ` Petr Vorel
2021-07-14 13:15 ` Richard Palethorpe
2021-07-21 15:43 ` Petr Vorel
2021-07-14 10:54 ` Petr Vorel
2021-07-14 13:26 ` Richard Palethorpe
2021-07-14 14:34 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 4/8] doc: Remind authors and maintainers to run make check Richard Palethorpe
2021-07-14 10:56 ` Petr Vorel
2021-07-14 13:34 ` Richard Palethorpe
2021-07-14 14:30 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 5/8] doc: Document TEST macro and state TST_RET/ERR rule LTP-002 Richard Palethorpe
2021-07-14 11:16 ` Petr Vorel
2021-07-14 13:37 ` Richard Palethorpe
2021-07-14 7:11 ` [LTP] [PATCH v2 6/8] Reference LTP-002 rule in Cocci scripts Richard Palethorpe
2021-07-14 11:18 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 7/8] API: Move libtsc.h from realtime tests include to tst_tsc.h Richard Palethorpe
2021-07-14 11:21 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 8/8] API/tst_tsc: Add guards and remove some boilerplate Richard Palethorpe
2021-07-14 11:22 ` Petr Vorel
2021-07-14 11:23 ` [LTP] [PATCH v2 0/8] Sparse based checker and rule proposal Petr Vorel
2021-07-14 13:43 ` Richard Palethorpe
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=YO6/0+gPhMh/mbW7@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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.