From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) by sourceware.org (Postfix) with ESMTPS id 174453858D28 for ; Mon, 19 Dec 2022 21:19:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 174453858D28 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 cmgw10.mail.unifiedlayer.com (unknown [10.0.90.125]) by progateway6.mail.pro1.eigbox.com (Postfix) with ESMTP id 90A4D10047D8B for ; Mon, 19 Dec 2022 21:18:55 +0000 (UTC) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with ESMTP id 7NXDpIjOWUBlf7NXDpf3gL; Mon, 19 Dec 2022 21:18:55 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=P6f/OgMu c=1 sm=1 tr=0 ts=63a0d53f 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=i7ilmSUZRu3pHDHmQyMA: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=AxmvQqg1edeMYL66QGSkRbgOlniyGdTsEPZsVUivXcw=; b=yOzBcWvO1Zdk0PRzdfCR6YODUe OQi82gnH7nPDgU6eN9/WR5GKjmOxxRlibW/Qn4V3KwnZGgQm3IoDh7YA71TifQYLKQtlurVCERXb5 mXF79dmsKmbGu/rpTRkxILJxe; Received: from 97-122-76-186.hlrn.qwest.net ([97.122.76.186]:55798 helo=murgatroyd) by box5379.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1p7NXD-002iNd-6E; Mon, 19 Dec 2022 14:18:55 -0700 From: Tom Tromey To: Eli Zaretskii via Gdb-patches Cc: Luis Machado , Tom Tromey , Eli Zaretskii 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> X-Attribution: Tom Date: Mon, 19 Dec 2022 14:18:52 -0700 In-Reply-To: <835ye7e9jw.fsf@gnu.org> (Eli Zaretskii via Gdb-patches's message of "Mon, 19 Dec 2022 16:45:55 +0200") Message-ID: <87h6xrks77.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: 97.122.76.186 X-Source-L: No X-Exim-ID: 1p7NXD-002iNd-6E X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: 97-122-76-186.hlrn.qwest.net (murgatroyd) [97.122.76.186]:55798 X-Source-Auth: tom+tromey.com X-Email-Count: 4 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTM3OS5ibHVlaG9zdC5jb20= X-Local-Domain: yes X-Spam-Status: No, score=-3022.2 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" == Eli Zaretskii via Gdb-patches writes: Eli> Tom, could you please chime in? What could explain such a slowdown Eli> using -readnow and in the MinGW build without worker threads (since Eli> GDB 12 didn't use threads, either)? And why -readnow is so different Eli> from a GDB built without threading? Just a quick answer for now, I haven't tried to reproduce or investigate... -readnow should not really be affected by the DWARF scanner rewrite. With -readnow, all the new code is bypassed anyway. For quite a while now, -readnow (when using DWARF anyway) has operated on the principle that since gdb is reading full symbols, it might as well not bother with partial symbols (or now, the index). Threads also should not matter here, because only the initial scan can use multiple threads. The full symbol reader is single-threaded and hasn't changed in any deep way since GDB 12. It's possible that some other change affected this -- the DWARF reader in general sees a lot of patches. I don't know which one it might be offhand, though. Tom