This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC 1/3] New make target 'check-perf' and new dir gdb.perf
- From: Tom Tromey <tromey at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Fri, 20 Sep 2013 12:59:25 -0600
- Subject: Re: [RFC 1/3] New make target 'check-perf' and new dir gdb.perf
- Authentication-results: sourceware.org; auth=none
- References: <520B7F70 dot 6070207 at codesourcery dot com> <1377663394-4975-1-git-send-email-yao at codesourcery dot com> <1377663394-4975-2-git-send-email-yao at codesourcery dot com>
Yao> +check-perf: all $(abs_builddir)/site.exp
Yao> + @if test ! -d gdb.perf; then mkdir gdb.perf; fi
Is this line really needed?
Just curious. I was thinking perhaps the parallel-mode approach to
outputs is preferable, but when running the perf tests parallel doesn't
make a whole lot of sense.
Yao> + $(DO_RUNTEST) --direcotry=gdb.perf --outdir gdb.perf $(RUNTESTFLAGS)
Typo, "--directory".
Tom