public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "annulen at yandex dot ru" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/26669] New: Use existing DWARF file as a reference for multifile mode
Date: Sun, 27 Sep 2020 11:42:02 +0000	[thread overview]
Message-ID: <bug-26669-11298@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26669

            Bug ID: 26669
           Summary: Use existing DWARF file as a reference for multifile
                    mode
           Product: dwz
           Version: unspecified
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: default
          Assignee: nobody at sourceware dot org
          Reporter: annulen at yandex dot ru
                CC: dwz at sourceware dot org
  Target Milestone: ---

I think it might be beneficial to add a modification to multifile mode,
allowing to "include" existing file as a "common file" and reference its DIEs
in file which is currently being optimized.

For example, there are Qt libraries, and we run dwz over all their debug info
and produce common file, e.g. qt_common.debug. This file contains information
about data types and macros which are commonly used in Qt APIs, so it's quite
likely that debug information of applications and libraries based on Qt will
also include same DIEs. So it seems to me that such feature would allow greater
deduplication of data while being scalable (each package can be optimized
separately)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2020-09-27 11:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-26669-11298@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=dwz@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).