mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-20 18:08:24 +08:00
Mention perf test in testsuite/README
gdb/testsuite: 2013-11-06 Yao Qi <yao@codesourcery.com> * README: Mention performance tests.
This commit is contained in:
@ -1,3 +1,7 @@
|
|||||||
|
2013-11-06 Yao Qi <yao@codesourcery.com>
|
||||||
|
|
||||||
|
* README: Mention performance tests.
|
||||||
|
|
||||||
2013-11-06 Yao Qi <yao@codesourcery.com>
|
2013-11-06 Yao Qi <yao@codesourcery.com>
|
||||||
|
|
||||||
* lib/perftest.exp: New.
|
* lib/perftest.exp: New.
|
||||||
|
@ -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
|
(The `site.exp' file contains a handful of useful variables like host
|
||||||
and target triplets, and pathnames.)
|
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
|
Testsuite Parameters
|
||||||
********************
|
********************
|
||||||
|
|
||||||
@ -315,6 +338,10 @@ Tests that exercise a specific GDB subsystem in more depth. For
|
|||||||
instance, gdb.disasm exercises various disassemblers, while
|
instance, gdb.disasm exercises various disassemblers, while
|
||||||
gdb.stabs tests pathways through the stabs symbol reader.
|
gdb.stabs tests pathways through the stabs symbol reader.
|
||||||
|
|
||||||
|
gdb.perf
|
||||||
|
|
||||||
|
GDB performance tests.
|
||||||
|
|
||||||
Writing Tests
|
Writing Tests
|
||||||
*************
|
*************
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user