From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Mike Stump <mikestump@comcast.net>
Cc: Nathan Froyd <nfroyd@mozilla.com>,
gcc-patches@gcc.gnu.org, jason@redhat.com
Subject: Re: [PATCH] parallelize g++ testing a bit more
Date: Mon, 20 Jun 2011 11:11:00 -0000 [thread overview]
Message-ID: <ydd62o0rccg.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <F7F1A044-C67D-4E4B-A0CA-08FD1A84B31A@comcast.net> (Mike Stump's message of "Fri, 17 Jun 2011 17:20:23 -0700")
Mike Stump <mikestump@comcast.net> writes:
> On Jun 17, 2011, at 10:47 AM, Nathan Froyd wrote:
>> I've done a lot of g++-only testsuite runs lately
>
> I think it is reasonable to have even more of them, say, if you have
> 16 cores and just test c++... I wonder what the scaling is like as we
> approach larger N. :-)
I've got a patch to do this, prompted by the use of UltraSPARC-T2
machines with 8 cores/8 strands which are quite slow on their own:
[build, testsuite, v3] Increase gcc, g++, gfortran and libstdc++-v3 testsuite parallelism
http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01633.html
but haven't yet incorporated Jakub's comments.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-06-20 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 18:01 Nathan Froyd
2011-06-17 18:38 ` Jason Merrill
2011-06-18 2:06 ` Mike Stump
2011-06-20 11:11 ` Rainer Orth [this message]
2011-06-20 13:41 ` Mike Stump
2011-06-20 13:33 ` Jason Merrill
2011-06-20 14:02 ` Jakub Jelinek
2011-06-20 22:03 ` [PATCH] parallelize gcc, gfortran and libstdc++ testing some more Jakub Jelinek
2011-06-21 7:09 ` Jason Merrill
2011-06-22 13:55 ` Jeff Law
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=ydd62o0rccg.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=mikestump@comcast.net \
--cc=nfroyd@mozilla.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).