From: Tom Tromey <tromey@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [0/7] RFC: read DWARF psymtabs in the background
Date: Tue, 15 Jun 2010 03:00:00 -0000 [thread overview]
Message-ID: <m31vc9xao6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C169EB0.6060405@vmware.com> (Michael Snyder's message of "Mon, 14 Jun 2010 14:27:12 -0700")
>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
>> All the code is written so that threads are optional. On platforms
>> without threads, everything works as before, albeit in a somewhat more
>> convoluted way.
Michael> Just curious; which platform without threads have you tested on?
I haven't run the test suite threadless at all.
However, I did build it without thread support (on Linux) and then
smoke-tested it by running it on itself.
I'm thinking of adding a --disable-threads or something so that people
who don't want this can turn it off.
Tom
next prev parent reply other threads:[~2010-06-15 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 18:22 Tom Tromey
2010-06-14 21:27 ` Michael Snyder
2010-06-15 3:00 ` Tom Tromey [this message]
2010-06-22 20:06 ` Mark Kettenis
2010-06-25 21:03 ` Tom Tromey
2010-06-25 21:36 ` 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=m31vc9xao6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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