From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] fix gdb.arch to be parallel-safe
Date: Wed, 14 Aug 2013 08:33:00 -0000 [thread overview]
Message-ID: <520B40C7.4050501@redhat.com> (raw)
In-Reply-To: <1376427803-16608-6-git-send-email-tromey@redhat.com>
On 08/13/2013 10:03 PM, Tom Tromey wrote:
> This fixes parts of gdb.arch to be parallel-safe.
> I only changed the bits I could test on this machine.
>
> I don't have access to many of the machines needed to fully switch
> gdb.arch; but I am happy to provide advice to others attempting this.
> Or, I can send an untested patch to convert it all.
If you're willing, the latter would be better, IMO. Best would be
publish a git branch and give a week or two for people to test.
My reasoning is that otherwise, we'll just end up with yet another
partial conversion. If some port goes untested, and the patch
breaks something in the testsuite for that port, then whoever cares for
the platform should notice it when she next runs tests on the platform.
If nobody cares for the platform, and doesn't run tests, well, then
it's okay to break it, as nobody cares...
--
Pedro Alves
next prev parent reply other threads:[~2013-08-14 8:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 21:03 [PATCH 0/5] more parallelization fixes Tom Tromey
2013-08-13 21:03 ` [PATCH 4/5] fix gdb.python to be parallel-safe Tom Tromey
2013-08-14 8:33 ` Pedro Alves
2013-08-14 16:20 ` Tom Tromey
2013-08-13 21:03 ` [PATCH 3/5] use standard_temp_file in another caching proc Tom Tromey
2013-08-13 21:03 ` [PATCH 2/5] introduce gdb_remote_download and finish parallel fixes in gdb.dwarf2 Tom Tromey
2013-08-26 2:20 ` Yao Qi
2013-08-26 15:54 ` Tom Tromey
2013-08-27 0:20 ` Yao Qi
2013-08-13 21:03 ` [PATCH 5/5] fix gdb.arch to be parallel-safe Tom Tromey
2013-08-14 8:33 ` Pedro Alves [this message]
2013-08-14 17:12 ` Tom Tromey
2013-08-13 21:03 ` [PATCH 1/5] fix some gdb.dwarf2 tests for parallel safety Tom Tromey
2013-08-27 15:16 ` Testsuite regression for fission + gdbindex run [Re: [PATCH 1/5] fix some gdb.dwarf2 tests for parallel safety] Jan Kratochvil
2013-08-14 8:34 ` [PATCH 0/5] more parallelization fixes Pedro Alves
2013-08-22 13:34 ` Tom Tromey
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=520B40C7.4050501@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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).