From: Nathan Froyd <nfroyd@mozilla.com>
To: gcc-patches@gcc.gnu.org
Cc: jason@redhat.com
Subject: [PATCH] parallelize g++ testing a bit more
Date: Fri, 17 Jun 2011 18:01:00 -0000 [thread overview]
Message-ID: <20110617174709.GA3443@nightcrawler> (raw)
I've done a lot of g++-only testsuite runs lately and I noticed that it
didn't parallelize all that well. The patch below adds a couple more
.exp files to the parallel infrastructure. dg-torture.exp is the big
one; it takes about as much time as old-deja.exp.
Other valid candidates are lto.exp and debug.exp, but the patch cuts g++
testing time in half as-is, so I felt it was a sufficient stopping
point.
OK to commit?
-Nathan
gcc/cp/
* Make-lang.in (check_g++_parallelize): Add more .exp files.
diff --git a/gcc/cp/Make-lang.in b/gcc/cp/Make-lang.in
index 45efd67..95bae37 100644
--- a/gcc/cp/Make-lang.in
+++ b/gcc/cp/Make-lang.in
@@ -154,7 +154,7 @@ check-c++-subtargets : check-g++-subtargets
lang_checks += check-g++
lang_checks_parallelized += check-g++
# For description see comment above check_gcc_parallelize in gcc/Makefile.in.
-check_g++_parallelize = old-deja.exp dg.exp
+check_g++_parallelize = old-deja.exp dg.exp dg-torture.exp struct-layout-1.exp
#\f
# Install hooks:
next reply other threads:[~2011-06-17 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 18:01 Nathan Froyd [this message]
2011-06-17 18:38 ` Jason Merrill
2011-06-18 2:06 ` Mike Stump
2011-06-20 11:11 ` Rainer Orth
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=20110617174709.GA3443@nightcrawler \
--to=nfroyd@mozilla.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).