From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/4] Perf test framework
Date: Fri, 01 Nov 2013 20:46:00 -0000 [thread overview]
Message-ID: <877gcryhnz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1383291300-13917-3-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Fri, 1 Nov 2013 15:34:58 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> + # Compile source files of test case. BODY is the tcl code to do
Yao> + # actual compilation and it should invoke 'PerfTest::compiled' if
Yao> + # compilation is successful.
Why not just have the body return success or failure and avoid having to
call another method?
Yao> + # The top-level interface to PerfTest.
Yao> + # COMPILE is the tcl code to generate and compile source files.
Yao> + # STARTUP is the tcl code to start up GDB.
Yao> + # RUN is the tcl code to drive GDB to do some operations.
Yao> + proc assemble {compile startup run} {
This approach ends up using a lot of indentation, it seems to me.
Slimmer approaches seem possible without losing anything.
E.g., in patch #4 I see:
+PerfTest::assemble {
+ compile {
+ for {set i 0} {$i < $SOLIB_COUNT} {incr i} {
+
But it seems to me that the "compile" part there is strictly redundant.
We already know that this is the "compile" branch, so why not have
"assemble" supply that?
Then the above would read:
PerfTest::assemble {
for {set i 0} {$i < $SOLIB_COUNT} {incr i} {
...
Tom
next prev parent reply other threads:[~2013-11-01 20:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 7:36 [PATCH 0/4 V4] GDB Performance testing Yao Qi
2013-11-01 7:36 ` [PATCH 2/4] Perf test framework Yao Qi
2013-11-01 19:43 ` Doug Evans
2013-11-01 20:46 ` Tom Tromey [this message]
2013-11-02 2:42 ` Yao Qi
2013-11-04 16:27 ` Tom Tromey
2013-11-06 5:30 ` Yao Qi
2013-11-01 7:36 ` [PATCH 4/4] Test on solib load and unload Yao Qi
2013-11-01 20:35 ` Tom Tromey
2013-11-02 2:50 ` Yao Qi
2013-11-04 17:37 ` Tom Tromey
2013-11-01 7:36 ` [PATCH 1/4] New make target 'check-perf' and new dir gdb.perf Yao Qi
2013-11-01 7:36 ` [PATCH 3/4] Mention perf test in testsuite/README Yao Qi
2013-11-06 6:42 ` [PATCH 0/4 V4] GDB Performance testing Yao Qi
-- strict thread matches above, loose matches on Subject: below --
2013-10-16 7:10 [PATCH 0/4 V3] " Yao Qi
2013-10-16 7:10 ` [PATCH 2/4] Perf test framework Yao Qi
2013-10-16 9:05 ` Yao Qi
2013-10-24 14:20 ` Yao Qi
2013-10-25 6:33 ` Doug Evans
2013-10-25 6:32 ` Doug Evans
2013-10-25 8:57 ` 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=877gcryhnz.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/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