From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: RFC: parallelize "make check"
Date: Thu, 25 Jun 2009 22:58:00 -0000 [thread overview]
Message-ID: <200906252359.02953.pedro@codesourcery.com> (raw)
In-Reply-To: <m34ou5ig9e.fsf@fleche.redhat.com>
On Wednesday 24 June 2009 20:27:41, Tom Tromey wrote:
> After running the tests in parallel, it combines them using a script
> from gcc's contrib directory. I just copied this into gdb/testsuite/,
> but that might not be best.
Of course, the best solution is to put gcc/contrib in its own git
repository and share it with gdb. :-P
[[[ seriously, am I the only one that would prefer that gdb and
the whole of src move into the same repository as gcc, which
would allow easier sharing of code between the projects, and
more easily spring up new shared libraries? Think reusing
bits of gcc in gdb :-) (other than libiberty). Wasn't svn gaining
support for modules a-la cvs? ]]]
Okay, sorry for hijacking. Please ignore. Great stuff, Tom!
--
Pedro Alves
next prev parent reply other threads:[~2009-06-25 22:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 19:27 Tom Tromey
2009-06-25 3:15 ` Eli Zaretskii
2009-06-25 20:21 ` Tom Tromey
2009-06-26 6:53 ` Eli Zaretskii
2009-06-26 15:56 ` Tom Tromey
2009-06-27 9:13 ` Eli Zaretskii
2009-06-25 14:55 ` Joel Brobecker
2009-06-25 15:09 ` Tom Tromey
2009-06-25 22:58 ` Pedro Alves [this message]
2009-06-26 1:34 ` Daniel Jacobowitz
2009-06-26 17:45 ` Tom Tromey
2009-06-26 20:27 ` Joseph S. Myers
2009-06-26 23:41 ` Joel Brobecker
2009-06-29 16:43 ` Tom Tromey
2009-06-29 16:57 ` Daniel Jacobowitz
2009-06-29 18:05 ` Tom Tromey
2009-06-29 18:38 ` Daniel Jacobowitz
2009-06-29 21:17 ` Jan Kratochvil
2009-07-01 12:06 ` [patch] testsuite: Fix multiple runs in parallel on a single host [Re: RFC: parallelize "make check"] Jan Kratochvil
2009-07-06 18:39 ` Tom Tromey
2009-07-06 18:53 ` [patch] testsuite: Fix multiple runs in parallel on a single host Jan Kratochvil
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=200906252359.02953.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--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