From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id rG2nL8AhpWNxnAcAWB0awg (envelope-from ) for ; Thu, 22 Dec 2022 22:34:24 -0500 Received: by simark.ca (Postfix, from userid 112) id B905C1E222; Thu, 22 Dec 2022 22:34:24 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=OjxCDhhg; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-8.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_HI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 629E81E0D3 for ; Thu, 22 Dec 2022 22:34:24 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id B6F5C385B50B for ; Fri, 23 Dec 2022 03:34:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B6F5C385B50B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1671766462; bh=MdIw9agSETPZV+wzGuDagULlHDLWwNM3/VYklOPiEzo=; h=Date:Subject:To:Cc:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=OjxCDhhgAcNTmva2qgelEhQLUZcThxgYwTiGaIPZhs5r34+LIOfRH/iF/LS0CNEbI EXdLWW6Ub3RLry0Nh/zQ6wBpl0Pa4MTsodNp4/7idqRz/gonEC1GuoCwFmwxSDMR+j AwZLFEoSQH3QdRgbuOT6eWMO2UguyInRKMmza1Kk= Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 25E6E3858D1E for ; Fri, 23 Dec 2022 03:34:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 25E6E3858D1E Received: from [10.0.0.11] (unknown [217.28.27.60]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 178761E0D3; Thu, 22 Dec 2022 22:34:01 -0500 (EST) Message-ID: Date: Thu, 22 Dec 2022 22:34:01 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: Two observations using GDB 13 snapshot Content-Language: en-US To: Eli Zaretskii , Tom Tromey Cc: gdb-patches@sourceware.org, luis.machado@arm.com 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> In-Reply-To: <83mt7idacj.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 12/19/22 22:26, Eli Zaretskii via Gdb-patches wrote: >> From: Tom Tromey >> Cc: Luis Machado , Tom Tromey , Eli >> Zaretskii >> Date: Mon, 19 Dec 2022 14:18:52 -0700 >> >>>>>>> "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. > > So you are saying that the rewrite of the DWARF scanner could be the > reason for the slowness? > > Let me know if I can provide any additional information that could be > useful in investigating this. Just wondering, do you build with or without optimizations? Simon