From: Patrick Palka <patrick@parcs.ath.cx>
To: Doug Evans <dje@google.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 5/8] gen-pert-test: parallel build support
Date: Sat, 25 Jul 2015 16:44:00 -0000 [thread overview]
Message-ID: <CA+C-WL_XUcyuqYQp4dSuzUgTUZk0DgLY76nc_9KGpLZ2zLjGdg@mail.gmail.com> (raw)
In-Reply-To: <001a11c301ba95cb5e051b62da63@google.com>
On Tue, Jul 21, 2015 at 9:44 AM, Doug Evans <dje@google.com> wrote:
> Hi.
>
> This patch adds parallel build support for perf testcases.
> To use the existing machinery, GDB_PARALLEL now contains
> the subdirectory in which to put the parallel builds.
>
> 2015-07-20 Doug Evans <dje@google.com>
>
> * Makefile.in (check/%.exp): Pass directory for GDB_PARALLEL.
> (workers/%.worker, build-perf): New rule.
> (GDB_PERFTEST_MODE): New variable.
> (check-perf): Use it.
> (clean): Clean up gdb.perf parallel build subdirs.
> * lib/build-piece.exp: New file.
> * lib/cache.exp (gdb_do_cache): Include $GDB_PARALLEL in path name.
> * lib/gdb.exp (standard_output_file): Include $GDB_PARALLEL in path
> name.
> (standard_temp_file): Ditto.
> (GDB_PARALLEL handling): Make outputs,temp,cache directories as
> subdirs
> of $GDB_PARALLEL.
This patch seems to have caused a number of regressions:
http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m64/builds/1502
http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/1501
http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/1510
(possibly among others)
Reverting this patch locally makes the regressions disappear for me,
at least on x86_64-m64.
next prev parent reply other threads:[~2015-07-25 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 13:44 Doug Evans
2015-07-25 16:44 ` Patrick Palka [this message]
2015-07-25 18:25 ` Doug Evans
2015-07-25 18:39 ` Patrick Palka
2015-07-25 23:21 ` Sergio Durigan Junior
2015-07-25 18:59 ` Doug Evans
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=CA+C-WL_XUcyuqYQp4dSuzUgTUZk0DgLY76nc_9KGpLZ2zLjGdg@mail.gmail.com \
--to=patrick@parcs.ath.cx \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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