From: Mark Wielaard <mark@klomp.org>
To: Aaron Merey <amerey@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH 1/2] libdw: Use INTUSE with dwarf_get_units
Date: Fri, 22 Dec 2023 00:56:20 +0100 [thread overview]
Message-ID: <20231221235620.GA6896@gnu.wildebeest.org> (raw)
In-Reply-To: <20231207013504.40300-2-amerey@redhat.com>
Hi Aaron,
On Wed, Dec 06, 2023 at 08:35:03PM -0500, Aaron Merey wrote:
> Add INTDECL for dwarf_get_units and call dwarf_get_units with INTUSE.
This is obviously OK. Although it is a bit of a micro-optimization.
Thanks,
Mark
next prev parent reply other threads:[~2023-12-21 23:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 1:35 [PATCH 0/2] dwarf_getaranges: Build aranges list from CUs Aaron Merey
2023-12-07 1:35 ` [PATCH 1/2] libdw: Use INTUSE with dwarf_get_units Aaron Merey
2023-12-21 23:56 ` Mark Wielaard [this message]
2023-12-22 21:02 ` Aaron Merey
2023-12-07 1:35 ` [PATCH 2/2] dwarf_getaranges: Build aranges list from CUs instead of .debug_aranges Aaron Merey
2023-12-11 23:18 ` [PATCH v2] " Aaron Merey
2024-02-13 13:28 ` Mark Wielaard
2024-02-20 4:20 ` Aaron Merey
2024-02-20 22:23 ` Mark Wielaard
2024-02-22 3:19 ` Aaron Merey
2024-02-22 15:35 ` Frank Ch. Eigler
2024-02-22 17:27 ` Aaron Merey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231221235620.GA6896@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=amerey@redhat.com \
--cc=elfutils-devel@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).