From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 56EEF3858D1E for ; Thu, 22 Feb 2024 15:35:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 56EEF3858D1E Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 56EEF3858D1E Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1708616135; cv=none; b=BI4BtZ1cmeNZiwaQzlFWmLe+Eb+DyVLAUs+DI3O1Ja0Ml0MZ3w+WIBjtRA/54zrfpPe5MobRguNZBNMIcS1eAV3mIlQpYYyHn1L5U5agr8XfAm+vOOZoejmcyymESnIJoc3jvf4fkDPHvDqnx3k/4d6OciPkPOj9Po9rz4kf3tM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1708616135; c=relaxed/simple; bh=DD9najY490xt1052niX2S8RIIdrpNXvFFcRn8Y/zdpg=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=eMP3Tb1Wy8Razxr4p1Oa5Uro8hSWNur+zWehAewPtwOIKT00V9hPca1uhqAvQ0w3n6zX8QCKc3qTn0ng/w5ljtQdgKtdjXFIAR0aoeKuIFBydZ7vmllxqC9JE/j6qoG8gK2Kc9LVMdqvzhldTaUluyGbOALwt3eFP9uK/5barQI= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1708616133; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5TKI6RuPO1w6zAz/hMlz337Emu2Kk2xJuOPssfIYanE=; b=fwgcsJTOqmt/ScbQR+syI2EzHgZsGKgHsc6PqhcmAF3F5a9o60ML6ArkLitOLB7nKRemhX lhZABR8n7RCfo/4V9dnK2eg2dbLGy6GF5SLMmQcobtClB6KPRw7q+/ZydgtPUI3QWi0bgi v0zTAf2m+aXq6cGiFH0F172+Fj6cTb4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-440-0f-tuzGIOVWipOEINXxiCQ-1; Thu, 22 Feb 2024 10:35:31 -0500 X-MC-Unique: 0f-tuzGIOVWipOEINXxiCQ-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3B7F688F2EC; Thu, 22 Feb 2024 15:35:31 +0000 (UTC) Received: from redhat.com (unknown [10.22.16.10]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 07544112131D; Thu, 22 Feb 2024 15:35:31 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1rdB6f-0001Kc-Ts; Thu, 22 Feb 2024 10:35:29 -0500 Date: Thu, 22 Feb 2024 10:35:29 -0500 From: "Frank Ch. Eigler" To: Aaron Merey Cc: Mark Wielaard , elfutils-devel@sourceware.org Subject: Re: [PATCH v2] dwarf_getaranges: Build aranges list from CUs instead of .debug_aranges Message-ID: <20240222153529.GG21278@redhat.com> References: <20231207013504.40300-3-amerey@redhat.com> <20231211231853.116254-1-amerey@redhat.com> <20240220222332.GB1666@gnu.wildebeest.org> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-7.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi - > > We could then also introduce a new public function, dwarf_getdieranges > > (?) that does the new thing. But it doesn't have to be public on the > > first try as long as dwarf_addrdie and dwfl_module_addrdie work. (We > > might want to change the interface of dwarf_getdieranges so it can be > > "lazy" for example.) > > Ok this approach seems like the most flexible. Users can have both > .debug_aranges and CU-based aranges plus we don't have to change the > semantics of dwarf_getaranges. [...] Another option is to generate the .debug_aranges automatically, but only if it is absent from the input dwarf file. (An eu-readelf user can tell if it was synthetic or not, if it matters.) - FChE