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/6] testsuite speedup
Date: Sun, 28 May 2017 21:29:00 +0200 [thread overview]
Message-ID: <20170528192906.1023-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this series is to speedup the testsuite,
mainly by avoiding to unneedlessly spawn child processes.
The resulting speedup here is over 2.5, which is quite appreciable.
Luc Van Oostenryck (6):
testsuite: get all tags in once
testsuite: grep the expected output only when needed
testsuite: grep the output patterns only when needed
testsuite: use shell arithmetic instead of fork-execing expr
testsuite: remove unneeded './' before commands
testsuite: avoid fork+execing basename
validation/backend/arithmetic-ops.c | 2 +-
validation/backend/array.c | 2 +-
validation/backend/bitwise-ops.c | 2 +-
validation/backend/bool-test.c | 2 +-
validation/backend/cast.c | 2 +-
validation/backend/cmp-ops.c | 2 +-
validation/backend/extern.c | 2 +-
validation/backend/function-ptr.c | 2 +-
validation/backend/hello.c | 2 +-
validation/backend/int-cond.c | 2 +-
validation/backend/load-type.c | 2 +-
validation/backend/logical-ops.c | 2 +-
validation/backend/loop.c | 2 +-
validation/backend/loop2.c | 2 +-
validation/backend/ptrcast.c | 2 +-
validation/backend/store-type.c | 2 +-
validation/backend/struct-access.c | 2 +-
validation/backend/struct.c | 2 +-
validation/backend/sum.c | 2 +-
validation/backend/union.c | 2 +-
validation/backend/void-return-type.c | 2 +-
validation/prototype.c | 2 +-
validation/test-suite | 137 +++++++++++++++++++---------------
23 files changed, 97 insertions(+), 84 deletions(-)
--
2.13.0
next reply other threads:[~2017-05-28 19:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 19:29 Luc Van Oostenryck [this message]
2017-05-28 19:29 ` [PATCH 1/6] testsuite: get all tags in once Luc Van Oostenryck
2017-05-28 19:29 ` [PATCH 2/6] testsuite: grep the expected output only when needed Luc Van Oostenryck
2017-05-28 19:29 ` [PATCH 3/6] testsuite: grep the output patterns " Luc Van Oostenryck
2017-05-28 19:29 ` [PATCH 4/6] testsuite: use shell arithmetic instead of fork-execing expr Luc Van Oostenryck
2017-05-28 19:29 ` [PATCH 5/6] testsuite: remove unneeded './' before commands Luc Van Oostenryck
2017-05-28 19:29 ` [PATCH 6/6] testsuite: avoid fork+execing basename Luc Van Oostenryck
2017-05-28 22:04 ` [PATCH 0/6] testsuite speedup Ramsay Jones
2017-05-28 22:39 ` Luc Van Oostenryck
2017-05-29 1:44 ` Ramsay Jones
2017-06-01 9:16 ` Christopher Li
2017-06-01 14:05 ` Luc Van Oostenryck
2017-06-02 7:29 ` Christopher Li
2017-06-02 10:57 ` 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=20170528192906.1023-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;
as well as URLs for NNTP newsgroup(s).