This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] switch to fully parallel mode
- From: Doug Evans <dje at google dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Yao Qi <yao at codesourcery dot com>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Wed, 18 Sep 2013 15:15:38 -0700
- Subject: Re: [PATCH] switch to fully parallel mode
- Authentication-results: sourceware.org; auth=none
- References: <1377711392-20236-1-git-send-email-tromey at redhat dot com> <52218B63 dot 80805 at codesourcery dot com> <877gefxont dot fsf at fleche dot redhat dot com> <CADPb22Rkqetekn+piUm+zxMO8sVWeYFZoh2ThNsiw3Wn-v73MQ at mail dot gmail dot com> <871u4mue1e dot fsf at fleche dot redhat dot com>
On Wed, Sep 18, 2013 at 12:26 PM, Tom Tromey <tromey@redhat.com> wrote:
>>> Though perhaps gdb.perf tests ought to all just "self-exclude" if
>>> performance testing is not requested. Wouldn't that be needed so that
>>> plain "runtest" would continue to work, anyway?
>
> Doug> Agreed. Perf testing needs to be separable from "make check", and not
> Doug> included with a default "make check".
>
> Just to be sure we're agreeing to the same thing, what I am saying is
> that I think each gdb.perf/*.exp should start with:
>
> if {[blah blah perf not intended]} {
> return
> }
I don't have too strong an opinion on how it is achieved, but that
would be acceptable, yes.
[Given that one can run *just* the perf tests with, for example,
gdb.perf/*.exp.]
I can't ever imagine running both from one make-check myself, but
maybe others might.