From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) by sourceware.org (Postfix) with ESMTPS id A724E3858D35 for ; Tue, 27 Dec 2022 17:19:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A724E3858D35 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tromey.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tromey.com Received: from cmgw14.mail.unifiedlayer.com (unknown [10.0.90.129]) by progateway4.mail.pro1.eigbox.com (Postfix) with ESMTP id C81CC100474E0 for ; Tue, 27 Dec 2022 17:19:27 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id ADbrpbCVeSqkqADbrpdO0D; Tue, 27 Dec 2022 17:19:27 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=OKbiYQWB c=1 sm=1 tr=0 ts=63ab291f a=ApxJNpeYhEAb1aAlGBBbmA==:117 a=ApxJNpeYhEAb1aAlGBBbmA==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=sHyYjHe8cH0A:10:nop_rcvd_month_year a=Qbun_eYptAEA:10:endurance_base64_authed_username_1 a=CCpqsmhAAAAA:8 a=NkaWWpfl5hcKJ90T7wQA:9 a=ul9cdbp4aOFLsgKbc677:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References :Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=YFU5RKOZ0hcY/yiB2Egg8t899Q222rxbLAMU+nrY4F4=; b=gcrlrsNdI0G7r3aO7JPtOKiV3H IE8/GMlQQvHFna2SbnRUBm2l4zcgG9MzyYMXI2bU4IBrxoGstoXyTSnW58uoNl2Zh9s/bczTpBgwQ g1zpYmgOc5CN4HK6Rc8r+UYz6; Received: from [161.98.8.3] (port=47574 helo=prentzel) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1pADbr-000xBD-FI; Tue, 27 Dec 2022 10:19:27 -0700 From: Tom Tromey To: Eli Zaretskii Cc: Tom Tromey , gdb-patches@sourceware.org, luis.machado@arm.com Subject: Re: Two observations using GDB 13 snapshot References: <83h6xugc5v.fsf@gnu.org> <58b64bf8-90b6-d080-c060-d03761501199@arm.com> <83k02neezy.fsf@gnu.org> <835ye7e9jw.fsf@gnu.org> <87h6xrks77.fsf@tromey.com> <83mt7idacj.fsf@gnu.org> <87fsd4elb2.fsf@tromey.com> <83o7rs4qmg.fsf@gnu.org> X-Attribution: Tom Date: Tue, 27 Dec 2022 10:19:24 -0700 In-Reply-To: <83o7rs4qmg.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 24 Dec 2022 20:13:11 +0200") Message-ID: <87cz84dasj.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box5379.bluehost.com X-AntiAbuse: Original Domain - sourceware.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tromey.com X-BWhitelist: no X-Source-IP: 161.98.8.3 X-Source-L: No X-Exim-ID: 1pADbr-000xBD-FI X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: (prentzel) [161.98.8.3]:47574 X-Source-Auth: tom+tromey.com X-Email-Count: 2 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3021.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,JMQ_SPF_NEUTRAL,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Eli> All I'm interested in is to help you and others understand what could Eli> be the reason for slow reading of debug info at startup, so that it Eli> could be sped up at some point. Ok. I re-read the thread and I see that at the beginning you didn't mention -readnow. So, assuming that the -readnow stuff was a distraction... The new indexer should not be significantly slower even when single-threaded. On my machine, if I "maint set worker-threads 0" and then use a -O2 build of gdb, it's about as fast as the system /bin/gdb (which uses the old code). Old: (gdb) file ./gdb [...] Command execution time: 2.408843 (cpu), 2.130013 (wall) New: (gdb) file ./gdb [...] Command execution time: 2.858222 (cpu), 2.865426 (wall) This is only slightly worse. Now there is a known bug in some linkers when -g3 is used, which causes a pretty severe slowdown in gdb. See: https://sourceware.org/bugzilla/show_bug.cgi?id=27754 I would have thought that this could not affect your build. However I don't know for certain. Tom