From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] first batch of test suite updates
Date: Thu, 20 Jun 2013 17:28:00 -0000 [thread overview]
Message-ID: <871u7wzprq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <51C32879.1080004@redhat.com> (Pedro Alves's message of "Thu, 20 Jun 2013 17:06:17 +0100")
Pedro> I think I saw places in the context of the patches that could be
Pedro> made to use build_executable instead of gdb_compile, and didn't look
Pedro> tricky, but, this is all good forward progress as is!
Yeah, not all spots are easy to convert in this way, and after
processing many of them it is easy to miss a few.
Pedro> I tried skimming the series, but got extremely bored after
Pedro> patch #1. :-)
Later parts of the series are more exciting, though not by much.
I do have some fun numbers about the timings though :)
Tom
next prev parent reply other threads:[~2013-06-20 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 21:04 Tom Tromey
2013-06-19 21:04 ` [PATCH 4/7] test suite update - gdb.base/[hijklm] Tom Tromey
2013-06-19 21:04 ` [PATCH 3/7] test suite update - gdb.base/[efg] Tom Tromey
2013-06-19 21:04 ` [PATCH 7/7] test suite update - gdb.base/[t-z] Tom Tromey
2013-06-19 21:04 ` [PATCH 2/7] test suite update - gdb.base/[cd] Tom Tromey
2013-06-19 21:04 ` [PATCH 6/7] test suite update - gdb.base/s* Tom Tromey
2013-06-19 21:04 ` [PATCH 1/7] test suite update - gdb.base/[ab] Tom Tromey
2013-07-01 8:19 ` [patch] testsuite build regression on CentOS-5 [Re: [PATCH 1/7] test suite update - gdb.base/[ab]] Jan Kratochvil
2013-07-02 20:08 ` [commit] " Jan Kratochvil
2013-06-19 21:14 ` [PATCH 5/7] test suite update - gdb.base/[nopqr] Tom Tromey
2013-06-20 14:27 ` [PATCH 0/7] first batch of test suite updates Joel Brobecker
2013-06-20 16:19 ` Pedro Alves
2013-06-20 17:28 ` Tom Tromey [this message]
2013-06-27 17:38 ` Tom Tromey
2013-06-27 18:45 ` Tom Tromey
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=871u7wzprq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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