diff options
| -rw-r--r-- | gdb/testsuite/ChangeLog | 4 | ||||
| -rw-r--r-- | gdb/testsuite/README | 27 |
2 files changed, 31 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 4d20ff4..726bfca 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,5 +1,9 @@ 2013-11-06 Yao Qi <yao@codesourcery.com> + * README: Mention performance tests. + +2013-11-06 Yao Qi <yao@codesourcery.com> + * lib/perftest.exp: New. * gdb.perf/lib/perftest/__init__.py: New. * gdb.perf/lib/perftest/measure.py: New. diff --git a/gdb/testsuite/README b/gdb/testsuite/README index ec91b14..c17bd34 100644 --- a/gdb/testsuite/README +++ b/gdb/testsuite/README @@ -25,6 +25,29 @@ The second is to cd to the testsuite directory and invoke the DejaGnu (The `site.exp' file contains a handful of useful variables like host and target triplets, and pathnames.) +Running the Performance Tests +***************************** + +GDB Testsuite includes performance test cases, which are not run together +with other test cases, because performance test cases are slow and need +a quiet system. There are two ways to run the performance test cases. +The first is to do `make check-perf' in the main build directory: + + make check-perf RUNTESTFLAGS="solib.exp SOLIB_COUNT=8" + +The second is to cd to the testsuite directory and invoke the DejaGnu +`runtest' command directly. + + cd testsuite + make site.exp + runtest GDB_PERFTEST_MODE=both GDB_PERFTEST_TIMEOUT=4000 --directory=gdb.perf solib.exp SOLIB_COUNT=8 + +Only "compile", "run" and "both" are valid to GDB_PERFTEST_MODE. They +stand for "compile tests only", "run tests only", and "compile and run +tests" respectively. "both" is the default. GDB_PERFTEST_TIMEOUT +specify the timeout, which is 3000 in default. The result of +performance test is appended in `testsuite/perftest.log'. + Testsuite Parameters ******************** @@ -315,6 +338,10 @@ Tests that exercise a specific GDB subsystem in more depth. For instance, gdb.disasm exercises various disassemblers, while gdb.stabs tests pathways through the stabs symbol reader. +gdb.perf + +GDB performance tests. + Writing Tests ************* |