diff options
| author | Yao Qi <yao@codesourcery.com> | 2013-09-25 12:41:45 +0800 |
|---|---|---|
| committer | Yao Qi <yao@codesourcery.com> | 2013-11-06 13:10:37 +0800 |
| commit | 7636ccf9f2517bd3005c983de3c89f4861be04a5 (patch) | |
| tree | 0062b477805b7a963875e934d457fc6617e1cec1 /gdb/Makefile.in | |
| parent | 2bc56d66132a8d4a06520b0531b8708108197c9b (diff) | |
| download | gdb-7636ccf9f2517bd3005c983de3c89f4861be04a5.zip gdb-7636ccf9f2517bd3005c983de3c89f4861be04a5.tar.gz gdb-7636ccf9f2517bd3005c983de3c89f4861be04a5.tar.bz2 | |
New make target 'check-perf' and new dir gdb.perf
We add a new dir gdb.perf in testsuite for all performance tests.
However, current 'make check' logic will either run dejagnu in
directory testsuite or iterate all gdb.* directories which has *.exp
files. Both of them will run tests in gdb.perf. We want to achieve:
1) typical 'make check' should not run performance tests. In each perf
test case, GDB_PERFTEST_MODE is checked. If it doesn't exist, return.
2) run perf tests easily. We add a new makefile target 'check-perf'.
gdb:
2013-11-06 Yao Qi <yao@codesourcery.com>
* Makefile.in (check-perf): New target.
gdb/testsuite:
2013-11-06 Yao Qi <yao@codesourcery.com>
* Makefile.in (check-perf): New target.
* configure.ac (AC_OUTPUT): Output Makefile in gdb.perf.
* configure: Re-generated.
* gdb.perf/Makefile.in: New.
Diffstat (limited to 'gdb/Makefile.in')
| -rw-r--r-- | gdb/Makefile.in | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/gdb/Makefile.in b/gdb/Makefile.in index a9b3c64..011b1aa 100644 --- a/gdb/Makefile.in +++ b/gdb/Makefile.in @@ -1009,6 +1009,14 @@ check: force $(MAKE) $(TARGET_FLAGS_TO_PASS) check; \ else true; fi +check-perf: force + @if [ -f testsuite/Makefile ]; then \ + rootme=`pwd`; export rootme; \ + rootsrc=`cd $(srcdir); pwd`; export rootsrc; \ + cd testsuite; \ + $(MAKE) $(TARGET_FLAGS_TO_PASS) check-perf; \ + else true; fi + # The idea is to parallelize testing of multilibs, for example: # make -j3 check//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu} # will run 3 concurrent sessions of check, eventually testing all 10 |