From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112]) by sourceware.org (Postfix) with ESMTPS id 3E616386F41A; Tue, 9 Mar 2021 09:10:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3E616386F41A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mark@klomp.org Received: from librem (deer0x15.wildebeest.org [172.31.17.151]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 043E43001762; Tue, 9 Mar 2021 10:10:32 +0100 (CET) Received: by librem (Postfix, from userid 1000) id 752C2C3342; Tue, 9 Mar 2021 10:09:18 +0100 (CET) Date: Tue, 9 Mar 2021 10:09:18 +0100 From: Mark Wielaard To: Allan Sandfeld Jensen Cc: gcc@gcc.gnu.org, binutils@sourceware.org, dwz@sourceware.org Subject: Re: DWZ 0.14 released Message-ID: <20210309090918.GA28954@wildebeest.org> References: <9f72f4e2-10b8-ac32-565e-b96314911d66@suse.de> <7438883.9MRIfJ1mQo@twilight> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7438883.9MRIfJ1mQo@twilight> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: dwz@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Dwz mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2021 09:10:39 -0000 Hi Allan, On Tue, Mar 09, 2021 at 09:06:54AM +0100, Allan Sandfeld Jensen wrote: > Btw, question for gcc/binutils > > Any reason the work done by tools like dwz couldn't be done in the compiler or > linker? Seems a bit odd to have a post-linker that optimizes the generated > code, when optimizations should already be enabled. dwz does two kinds of optimization. First it attempts to optimize the DWARF debugging information for a given object (executable or shared library). Secondly it tries to put shared pieces of a list of given objects into a supplemental file that gets referenced from all the given object files. Technically the first optimization could be done by the linker. But the second optimization is really a post-linker step. Cheers, Mark