From: Yao Qi <yao@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] New make target 'check-perf' and new dir gdb.perf
Date: Thu, 10 Oct 2013 00:29:00 -0000 [thread overview]
Message-ID: <5255F47F.1050209@codesourcery.com> (raw)
In-Reply-To: <CADPb22Rrpa7_M9E-+LXP+K6cXFDErypUU1pehO0tJy1eZ=TfhQ@mail.gmail.com>
On 10/09/2013 01:13 PM, Doug Evans wrote:
> I realize this is cut-n-paste-n-tweaking existing code,
> I'm just curious under what scenario the mkdir is needed (except for a
> broken build tree).
>
These dirs (testsuite/gdb.*) are there after configure and make.
>> >+ $(DO_RUNTEST) --directory=gdb.perf --outdir gdb.perf $(RUNTESTFLAGS) GDB_PERFORMANCE=yes
> I don't know if it'll ever be useful, but if GDB_PERFORMANCE=yes
> appears before RUNTESTFLAGS, then it can be overridden on the command
> line.
>
We should have the flexibility to set GDB_PERFORMANCE=yes|compile|run in
the command line.
>
> I was thinking there is one time when IWBN to run the tests in parallel:
> If I make a change to the test harness, I may want to run all the
> tests in some reduced-size mode to verify I haven't broken anything.
> I won't care what the perf results are - I'll just want to know that
> things still work.:-) This can be left for later though.
Or we can add some test cases to perf test harness, and they can be
started by 'make check' too.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-10-10 0:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 14:27 [PATCH 0/3 V2] GDB Performance testing Yao Qi
2013-09-25 14:27 ` [PATCH 1/3] New make target 'check-perf' and new dir gdb.perf Yao Qi
2013-10-09 5:13 ` Doug Evans
2013-10-10 0:29 ` Yao Qi [this message]
2013-10-15 17:14 ` Doug Evans
2013-09-25 14:27 ` [PATCH 3/3] Test on solib load and unload Yao Qi
2013-09-27 14:09 ` Gary Benson
2013-09-27 15:16 ` Yao Qi
2013-09-27 15:50 ` Gary Benson
2013-09-25 14:27 ` [PATCH 2/3] Perf test framework Yao Qi
2013-10-09 6:37 ` Doug Evans
2013-10-10 3:04 ` Yao Qi
2013-10-15 20:14 ` Doug Evans
2013-10-06 1:44 ` [PATCH 0/3 V2] GDB Performance testing Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5255F47F.1050209@codesourcery.com \
--to=yao@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox