public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/33612] make check -jN should fully use N cores
Date: Mon, 25 Feb 2008 17:29:00 -0000	[thread overview]
Message-ID: <20080225172838.30866.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33612-365@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from bkoz at gcc dot gnu dot org  2008-02-25 17:28 -------

Jason has suggested a good idea to fix this without messing about with test
harness issues.

We can just split

make check 

up into 

make check1
make check2
make check3
make check4
make check5
make check6
...

where the old "make check" is equivalent to make check[1-n] in terms of test
coverage. This will allow 

make -j4 check

to run

make check1
make check2
make check3
make check4

all at the same time.

This should speed things up greatly on current hardware.

Seems simple enough: I feel a bit silly for not having thought of this before.
This is of relatively high priority given the time requirement for libstdc++
testing. 

-benjamin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33612


  parent reply	other threads:[~2008-02-25 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 18:21 [Bug libstdc++/33612] New: " bkoz at gcc dot gnu dot org
2007-10-01 18:21 ` [Bug libstdc++/33612] " bkoz at gcc dot gnu dot org
2007-10-01 18:30 ` pinskia at gcc dot gnu dot org
2008-02-25 17:29 ` bkoz at gcc dot gnu dot org [this message]
2008-02-25 18:10 ` pcarlini at suse dot de
2009-01-08 22:47 ` bkoz at gcc dot gnu dot org
     [not found] <bug-33612-4@http.gcc.gnu.org/bugzilla/>
2022-01-04  5:29 ` egallager at gcc dot gnu.org

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=20080225172838.30866.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).