From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 51103 invoked by alias); 9 Mar 2019 18:09:41 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 51094 invoked by uid 89); 9 Mar 2019 18:09:41 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=signals, delivering X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 09 Mar 2019 18:09:40 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:33576) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h2gPi-0005Ny-Jr; Sat, 09 Mar 2019 13:09:38 -0500 Received: from [176.228.60.248] (port=4782 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h2gPf-0002SV-Sc; Sat, 09 Mar 2019 13:09:38 -0500 Date: Sat, 09 Mar 2019 18:09:00 -0000 Message-Id: <83tvgb7we9.fsf@gnu.org> From: Eli Zaretskii To: Tom Tromey CC: gdb-patches@sourceware.org In-reply-to: <20190309172300.2764-1-tom@tromey.com> (message from Tom Tromey on Sat, 9 Mar 2019 10:22:54 -0700) Subject: Re: [RFC 0/6] Demangle minimal symbol names in worker threads References: <20190309172300.2764-1-tom@tromey.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00217.txt.bz2 > From: Tom Tromey > 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.