From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/4 V4] GDB Performance testing
Date: Fri, 01 Nov 2013 07:36:00 -0000 [thread overview]
Message-ID: <1383291300-13917-1-git-send-email-yao@codesourcery.com> (raw)
Hi,
Here is the V4 of GDB performance testing. Doug approved V3 except
patch 2/4. V4 addresses review comments to V3, including Pedro's
suggestion on renaming parameters.
The changes in V4 can be found in each patch.
The basic usages of performance testing are,
$ make check-perf
$ make check-perf RUNTESTFLAGS="--target_board=native-gdbserver solib.exp"
$ make check-perf RUNTESTFLAGS="solib.exp SOLIB_COUNT=512"
We can skip compilation step like,
$ make check-perf RUNTESTFLAGS='solib.exp GDB_PERFTEST_MODE=run'
or only compile test cases,
$ make check-perf RUNTESTFLAGS='solib.exp GDB_PERFTEST_MODE=compile'
in default, GDB_PERFTEST_MODE=both.
If the perf test case takes much time, we can specify timeout by
GDB_PERFTEST_TIMEOUT=1000.
$ make check-perf RUNTESTFLAGS="--target_board=native-gdbserver GDB_PERFTEST_TIMEOUT=4000 solib.exp"
*** BLURB HERE ***
Yao Qi (4):
New make target 'check-perf' and new dir gdb.perf
Perf test framework
Mention perf test in testsuite/README
Test on solib load and unload
gdb/Makefile.in | 8 +
gdb/testsuite/Makefile.in | 4 +
gdb/testsuite/README | 27 ++++
gdb/testsuite/configure | 3 +-
gdb/testsuite/configure.ac | 2 +-
gdb/testsuite/gdb.perf/Makefile.in | 15 ++
gdb/testsuite/gdb.perf/lib/perftest/__init__.py | 17 +++
gdb/testsuite/gdb.perf/lib/perftest/measure.py | 146 ++++++++++++++++++++
gdb/testsuite/gdb.perf/lib/perftest/perftest.py | 73 ++++++++++
gdb/testsuite/gdb.perf/lib/perftest/reporter.py | 64 +++++++++
gdb/testsuite/gdb.perf/lib/perftest/testresult.py | 57 ++++++++
gdb/testsuite/gdb.perf/solib.c | 83 ++++++++++++
gdb/testsuite/gdb.perf/solib.exp | 85 ++++++++++++
gdb/testsuite/gdb.perf/solib.py | 73 ++++++++++
gdb/testsuite/lib/gdb.exp | 16 +++
gdb/testsuite/lib/perftest.exp | 148 +++++++++++++++++++++
16 files changed, 819 insertions(+), 2 deletions(-)
create mode 100644 gdb/testsuite/gdb.perf/Makefile.in
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/__init__.py
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/measure.py
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/perftest.py
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/reporter.py
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/testresult.py
create mode 100644 gdb/testsuite/gdb.perf/solib.c
create mode 100644 gdb/testsuite/gdb.perf/solib.exp
create mode 100644 gdb/testsuite/gdb.perf/solib.py
create mode 100644 gdb/testsuite/lib/perftest.exp
--
1.7.7.6
next reply other threads:[~2013-11-01 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 7:36 Yao Qi [this message]
2013-11-01 7:36 ` [PATCH 3/4] Mention perf test in testsuite/README Yao Qi
2013-11-01 7:36 ` [PATCH 1/4] New make target 'check-perf' and new dir gdb.perf Yao Qi
2013-11-01 7:36 ` [PATCH 2/4] Perf test framework Yao Qi
2013-11-01 19:43 ` Doug Evans
2013-11-01 20:46 ` Tom Tromey
2013-11-02 2:42 ` Yao Qi
2013-11-04 16:27 ` Tom Tromey
2013-11-06 5:30 ` Yao Qi
2013-11-01 7:36 ` [PATCH 4/4] Test on solib load and unload Yao Qi
2013-11-01 20:35 ` Tom Tromey
2013-11-02 2:50 ` Yao Qi
2013-11-04 17:37 ` Tom Tromey
2013-11-06 6:42 ` [PATCH 0/4 V4] GDB Performance testing Yao Qi
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=1383291300-13917-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.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