From: Alexandre Oliva <aoliva@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: add check// targets to gdb
Date: Thu, 03 Jun 2004 11:22:00 -0000 [thread overview]
Message-ID: <orfz9crimn.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <oroeo1qim6.fsf@livre.redhat.lsd.ic.unicamp.br>
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
On Jun 3, 2004, Alexandre Oliva <aoliva@redhat.com> wrote:
> BTW, I just found out the patch didn't quite work. There are some
> sub-subdirectories of testsuite that have to be configured as well.
> I'll post an update later.
Here's a fixed patch.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gdb-check-parallel.patch --]
[-- Type: text/x-patch, Size: 1893 bytes --]
Index: gdb/ChangeLog
from Alexandre Oliva <aoliva@redhat.com>
* Makefile.in (check//%): New.
Index: gdb/Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.581
diff -u -p -r1.581 Makefile.in
--- gdb/Makefile.in 26 May 2004 05:31:39 -0000 1.581
+++ gdb/Makefile.in 3 Jun 2004 11:21:20 -0000
@@ -956,6 +956,34 @@ check: force
$(MAKE) $(TARGET_FLAGS_TO_PASS) check; \
else true; fi
+# The idea is to parallelize testing of multilibs, for example:
+# make -j3 check//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
+# will run 3 concurrent sessions of check, eventually testing all 10
+# combinations. GNU make is required for the % pattern to work, as is
+# a shell that expands alternations within braces. If GNU make is not
+# used, this rule will harmlessly fail to match.
+check//%: force
+ @if [ -f testsuite/config.status ]; then \
+ rootme=`pwd`; export rootme; \
+ rootsrc=`cd $(srcdir); pwd`; export rootsrc; \
+ target=`echo "$@" | sed 's,//.*,,'`; \
+ variant=`echo "$@" | sed 's,^[^/]*//,,'`; \
+ vardots=`echo "$$variant" | sed 's,/,.,g'`; \
+ testdir=testsuite.$$vardots; \
+ if [ ! -f $$testdir/Makefile ]; then \
+ (cd testsuite && find . -name config.status) | \
+ sed s,/config.status$$,, | sort | while read subdir; do \
+ $(SHELL) $(srcdir)/../mkinstalldirs $$testdir/$$subdir && \
+ (cd $$testdir/$$subdir && \
+ $(SHELL) $$rootme/testsuite/$$subdir/config.status \
+ --recheck && \
+ $(SHELL) ./config.status); done; \
+ else :; fi && cd $$testdir && \
+ $(MAKE) $(TARGET_FLAGS_TO_PASS) \
+ RUNTESTFLAGS="--target_board=$$variant $(RUNTESTFLAGS)" \
+ "$$target"; \
+ else true; fi
+
info dvi install-info clean-info html install-html: force
@$(MAKE) $(FLAGS_TO_PASS) DO=$@ "DODIRS=$(SUBDIRS)" subdir_do
[-- Attachment #3: Type: text/plain, Size: 188 bytes --]
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2004-06-03 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 2:31 Alexandre Oliva
2004-06-03 3:17 ` Daniel Jacobowitz
2004-06-03 6:08 ` Alexandre Oliva
2004-06-03 11:22 ` Alexandre Oliva [this message]
2004-06-07 15:23 ` Daniel Jacobowitz
2004-06-07 20:08 ` Alexandre Oliva
2004-06-07 20:11 ` Daniel Jacobowitz
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=orfz9crimn.fsf@livre.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.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