This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC 0/6] Demangle minimal symbol names in worker threads
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Tom Tromey <tom at tromey dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 09 Mar 2019 20:09:02 +0200
- Subject: Re: [RFC 0/6] Demangle minimal symbol names in worker threads
- References: <20190309172300.2764-1-tom@tromey.com>
> From: Tom Tromey <tom@tromey.com>
> Date: Sat, 9 Mar 2019 10:22:54 -0700
>
> I've thought for a while that gdb should take advantage of multiple
> cores in order to speed up its processing. This series is some
> initial work in that direction.
>
> In particular, this patch arranges to do the demangling for minimal
> symbols in worker threads. I chose this because it seemed relatively
> simple to reason about, as the demangler is already mostly thread-safe
> (except, as it turns out, the Ada demangler, which is fixed in this
> series). It isn't actually a very important thing to speed up, as
> minimal symbol reading is already reasonably speedy; but I thought it
> best to start with something straightforward to facilitate flushing
> out thread safety bugs.
Thanks, but is std::thread portable enough? E.g., I recall problems
with it in MinGW.
Same question regarding delivering signals to threads.