From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Rename some test binaries
Date: Tue, 09 Jun 2009 18:12:00 -0000 [thread overview]
Message-ID: <20090609181228.GA26510@caradoc.them.org> (raw)
In-Reply-To: <m3ab4hl1t1.fsf@fleche.redhat.com>
On Tue, Jun 09, 2009 at 12:06:18PM -0600, Tom Tromey wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
>
> Daniel> I've checked in this obvious patch, which gives a number of affected
> Daniel> tests unique output files. They continue to share source files. I
> Daniel> didn't audit for every output file used by every test, but these are
> Daniel> the only cases I've seen fail.
>
> I think this also needs patches to all the Makefile.in's.
> Unless you want to take the opportunity to get rid of this stuff... :)
Are they actually current? If they are, I'll update them... last I
remember they were very stale.
> Daniel> We'd need a more thorough check if we were going to parallelize .exp
> Daniel> files.
>
> This sure would be nice.
I was looking at the rules GCC uses today. It looks like it would be
easy to migrate, but the Make goo involved is over my head. Splitting
gdb.base in half and then parallelizing the rest at directory
granularity should do a lot of good on a modern 4-way or 8-way system.
Want to give it a shot? :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-06-09 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 17:16 Daniel Jacobowitz
2009-06-09 18:06 ` Tom Tromey
2009-06-09 18:12 ` Daniel Jacobowitz [this message]
2009-06-09 18:49 ` 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=20090609181228.GA26510@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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