From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFC 0/6] Demangle minimal symbol names in worker threads
Date: Mon, 11 Mar 2019 22:39:00 -0000 [thread overview]
Message-ID: <87ef7d8298.fsf@tromey.com> (raw)
In-Reply-To: <83tvgb7we9.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 Mar 2019 20:09:02 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> Thanks, but is std::thread portable enough? E.g., I recall problems
Eli> with it in MinGW.
I asked around and learned that std::thread should work fine if you have
winpthreads, which apparently is used by default for mingw-w64.
I don't actually know much about the mingw world, so I don't know if
that is good enough or not. Could you say?
Jonathan Wakely also once wrote a port of libstdc++ to the Win32 API,
but couldn't find help with testing, so never checked it in.
Eli> Same question regarding delivering signals to threads.
If the signal thing is broken in this series, then it is probably
already broken today. However I think it ought to be ok as SEGV is a
synchronous signal; that is, it is delivered to the faulting thread.
Does that address your concern here?
Tom
next prev parent reply other threads:[~2019-03-11 22:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 17:23 Tom Tromey
2019-03-09 17:23 ` [RFC 6/6] Demangle minsyms in parallel Tom Tromey
2019-03-09 17:23 ` [RFC 3/6] Lock the demangled hash table Tom Tromey
2019-03-09 17:23 ` [RFC 4/6] Introduce run_on_main_thread Tom Tromey
2019-03-09 17:23 ` [RFC 1/6] Defer minimal symbol name-setting Tom Tromey
2019-03-09 17:23 ` [RFC 5/6] Introduce thread-safe way to handle SIGSEGV Tom Tromey
2019-03-11 17:24 ` John Baldwin
2019-03-09 17:23 ` [RFC 2/6] Remove static buffer from ada_decode Tom Tromey
2019-03-09 18:09 ` [RFC 0/6] Demangle minimal symbol names in worker threads Eli Zaretskii
2019-03-11 17:35 ` John Baldwin
2019-03-11 22:39 ` Tom Tromey [this message]
2019-03-12 3:33 ` Eli Zaretskii
2019-03-13 15:38 ` Eli Zaretskii
2019-03-15 23:28 ` Tom Tromey
2019-03-16 7:46 ` Eli Zaretskii
2019-03-16 8:31 ` Eli Zaretskii
2019-03-15 23:40 ` Tom Tromey
2019-03-16 7:52 ` Eli Zaretskii
2019-03-11 17:26 ` John Baldwin
2019-03-11 22:40 ` 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=87ef7d8298.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--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