From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 0/2] Libclang based analyzer
Date: Fri, 4 Jun 2021 11:15:38 +0200 [thread overview]
Message-ID: <YLnvOpNr3HlTLWWP@pevik> (raw)
In-Reply-To: <875yyuj91v.fsf@suse.de>
Hi Richie,
> > FYI yesterday I sent patch to add make check{,-c,shell}, but for running C/shell API tests:
> > https://patchwork.ozlabs.org/project/ltp/list/?series=247103
> So I guess we have a name collision here. Something to consider is that
> GNU Make defines 'checks' as running self tests. So perhaps you are
> correct to use that word.
> I could rename the static analyses to 'analyze' or 'lint'. OTOH it might
> be better if running the self tests is called 'make
> run-{c,shell}-api-tests', because only a few people need to do
> that. Whereas it is intended that all contributors run the static
> analyses checks.
run-{c,shell}-api-tests is IMHO too long, but I was thinking about
check-{,c,shell}-api. But maybe you're right, let's wait for others opinions.
> Although, if someone runs 'make check' in the lib directory, then it
> makes sense to run the C API tests as well as do the analyses. Or not?
Yes, I'd be for having make check, which would run all check targets,
which can be also run separately:
make check-clang
make check-c
make check-shell
(or whatever we name these clang and C/shell API tests targets)
> > Taking 2 latests commits + adding clang-devel / libclang-dev packages makes CI
> > running.
> > https://github.com/pevik/ltp/commit/b2427f39ddb15c97761208a605637e0da6fe66ca
> Thanks, I guess this shows that libclang is well supported.
Yes, it looks to be even in old clang 3.5.
> > The only missing piece is include/mk/clang-checks.mk (this patchset not even
> > compile now).
> >> Richard Palethorpe (2):
> >> Add 'make checks' and clang-checks to build system
> > make check ... clang-check (to avoid confusion).
> >> Start libclang based analyzer and TEST() check
> >> configure.ac | 2 +
> >> include/mk/config.mk.in | 5 +
> >> include/mk/env_post.mk | 8 ++
> >> include/mk/generic_leaf_target.inc | 5 +-
> >> include/mk/lib.mk | 3 +
> >> include/mk/rules.mk | 9 ++
> >> include/mk/testcases.mk | 1 +
> >> tools/clang-checks/.gitignore | 1 +
> >> tools/clang-checks/Makefile | 13 ++
> >> tools/clang-checks/main.c | 218 +++++++++++++++++++++++++++++
> > I'd name it tools/clang-check/ (and include/mk/clang-check.mk), but that's just
> > personal opinion.
> Yeah, we do not want a mixture of check and checks. I should probably
> just make it 'check' as it saves typing one letter.
+1
Kind regards,
Petr
next prev parent reply other threads:[~2021-06-04 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 15:48 [LTP] [RFC PATCH 0/2] Libclang based analyzer Richard Palethorpe
2021-06-03 15:48 ` [LTP] [RFC PATCH 1/2] Add 'make checks' and clang-checks to build system Richard Palethorpe
2021-06-04 6:06 ` Petr Vorel
2021-06-04 6:12 ` Petr Vorel
2021-06-04 8:42 ` Richard Palethorpe
2021-06-04 8:55 ` Petr Vorel
2021-06-03 15:48 ` [LTP] [RFC PATCH 2/2] Start libclang based analyzer and TEST() check Richard Palethorpe
2021-06-04 6:20 ` [LTP] [RFC PATCH 0/2] Libclang based analyzer Petr Vorel
2021-06-04 9:03 ` Richard Palethorpe
2021-06-04 9:15 ` Petr Vorel [this message]
2021-06-04 11:34 ` Cyril Hrubis
2021-06-04 12:51 ` Petr Vorel
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=YLnvOpNr3HlTLWWP@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.