This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Support 'make check-parallel' in gdb's build dir
- From: Simon Marchi <simon dot marchi at ericsson dot com>
- To: Pedro Alves <palves at redhat dot com>, <gdb-patches at sourceware dot org>
- Date: Thu, 11 Feb 2016 11:44:24 -0500
- Subject: Re: [PATCH] Support 'make check-parallel' in gdb's build dir
- Authentication-results: sourceware.org; auth=none
- References: <1455207502-11058-1-git-send-email-palves at redhat dot com>
On 16-02-11 11:18 AM, Pedro Alves wrote:
> +check-parallel: force
> + @if [ -f testsuite/Makefile ]; then \
> + rootme=`pwd`; export rootme; \
> + rootsrc=`cd $(srcdir); pwd`; export rootsrc; \
> + cd testsuite; \
> + $(MAKE) $(TARGET_FLAGS_TO_PASS) check-parallel; \
> + else true; fi
> +
Thanks for making it a little bit more convenient. I also use the check-parallel
target, it feels more natural than setting FORCE_PARALLEL.
> +Parallel testing
> +****************
> +
> +When testing natively (that is, not with a remote host), you can run
I know you just moved that text, but would you know by any chance what is
meant by "remote host" here? Is it host in the Autoconf/Dejagnu,
terminology?
For example, if I'm building on Linux a GDB that will run on Windows to
debug some bare-metal ARM, we are in presence of a remote host which is
Windows?
I understand why you couldn't run parallel tests against a single, bare-metal
target, but I don't understand why having a remote host would limit that
(assuming you can connect multiple times simultaneously to that remote host).