From: Ulf Hermann <ulf.hermann@qt.io>
To: Mark Wielaard <mark@klomp.org>, elfutils-devel@sourceware.org
Subject: Re: [PATCH 2/2 v2] Generalize cu_sec_idx
Date: Thu, 14 Dec 2017 13:53:00 -0000 [thread overview]
Message-ID: <7ba4e217-ebd7-1fea-31c7-5c2ff6ba166b@qt.io> (raw)
In-Reply-To: <1513259491.15696.82.camel@klomp.org>
On 12/14/2017 02:51 PM, Mark Wielaard wrote:
> This is clever and indeed cu_sec_idx () is not generic enough.
> But this is also somewhat inefficient. I am working on DWARF5 support
> and there a CU can come from even more different sections (or file). So
> I am changing Dwarf_CU to have an explicit section to which is it is
> associated. This can then also be used by the "fake" CUs like created
> in dwarf_getmacros.
Mind that the two most common cases are 0 and 1. In fact nothing else was supported before this change. So, most of the time this will not do a lot of iteration.
regards,
Ulf
next prev parent reply other threads:[~2017-12-14 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 15:06 Ulf Hermann
2017-12-14 13:51 ` Mark Wielaard
2017-12-14 13:53 ` Ulf Hermann [this message]
2017-12-20 18:09 ` Mark Wielaard
2017-12-21 13:48 ` Ulf Hermann
2017-12-21 20:22 ` Mark Wielaard
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=7ba4e217-ebd7-1fea-31c7-5c2ff6ba166b@qt.io \
--to=ulf.hermann@qt.io \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).