From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3484 invoked by alias); 20 Sep 2013 18:59:31 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 3473 invoked by uid 89); 20 Sep 2013 18:59:30 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 20 Sep 2013 18:59:30 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r8KIxRV4028120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 20 Sep 2013 14:59:27 -0400 Received: from barimba (ovpn-113-63.phx2.redhat.com [10.3.113.63]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r8KIxPQv001009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 20 Sep 2013 14:59:26 -0400 From: Tom Tromey To: Yao Qi Cc: Subject: Re: [RFC 1/3] New make target 'check-perf' and new dir gdb.perf References: <520B7F70.6070207@codesourcery.com> <1377663394-4975-1-git-send-email-yao@codesourcery.com> <1377663394-4975-2-git-send-email-yao@codesourcery.com> Date: Fri, 20 Sep 2013 18:59:00 -0000 In-Reply-To: <1377663394-4975-2-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Wed, 28 Aug 2013 12:16:32 +0800") Message-ID: <87bo3nqpyq.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-09/txt/msg00780.txt.bz2 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