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 8F63C3857C7A for ; Thu, 28 Jan 2021 22:59:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8F63C3857C7A 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 93D4E30010D9; Thu, 28 Jan 2021 23:59:51 +0100 (CET) Received: by librem (Postfix, from userid 1000) id 0D6E4C1749; Thu, 28 Jan 2021 23:58:44 +0100 (CET) Date: Thu, 28 Jan 2021 23:58:44 +0100 From: Mark Wielaard To: tbaeder@redhat.com Cc: elfutils-devel@sourceware.org Subject: Re: [PATCH 2/2] elf-from-memory: Refactor to get rid of nested function Message-ID: <20210128225843.GN8492@wildebeest.org> References: <20210108080956.2201985-1-tbaeder@redhat.com> <20210108080956.2201985-3-tbaeder@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210108080956.2201985-3-tbaeder@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-5.7 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: elfutils-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Elfutils-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 22:59:53 -0000 Hi Timm, On Fri, Jan 08, 2021 at 09:09:56AM +0100, Timm Bäder via Elfutils-devel wrote: > Try to unify the 32/64 bit code paths and get rid of the nested > handle_segment() this way. The new code does seem to do the same thing as the old code. Added a ChangeLog entry and pushed. Thanks, Mark