public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27440] New: [dwz, dwarf5] Add --dwarf-5 flag to generate .debug_sup, ref_sup and strp_sup
Date: Fri, 19 Feb 2021 11:43:28 +0000	[thread overview]
Message-ID: <bug-27440-11298@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27440
           Summary: [dwz, dwarf5] Add --dwarf-5 flag to generate
                    .debug_sup, ref_sup and strp_sup
           Product: dwz
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: nobody at sourceware dot org
          Reporter: mark at klomp dot org
                CC: dwz at sourceware dot org
            Blocks: 24726
  Target Milestone: ---

Currently the dwz multi-files are really DWARF4 + GNU extensions. Since the
format and references were formalized in the DWARF5 spec as DWARF Supplementary
Object Files (DWARF5 section 7.3.6) it would be nice to have a way to generate
this format with a --dwarf-5 flag:

- Use DW_FORM_ref_sup[48] and DW_FORM_strp_sup instead of
  DW_FORM_GNU_ref_alt and DW_FORM_GNU_strp_alt

- Generate .debug_sup section (standardized variant of .gnu_debugaltlink)


Referenced Bugs:

https://sourceware.org/bugzilla/show_bug.cgi?id=24726
[Bug 24726] [dwz] Support DWARF5
-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-02-19 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 11:43 mark at klomp dot org [this message]
2021-02-19 15:42 ` [Bug default/27440] " jakub at redhat dot com
2021-02-21  0:09 ` tromey at sourceware dot org
2021-02-21  0:29 ` jakub at redhat dot com
2021-02-21 23:19 ` tromey at sourceware dot org
2021-02-26 23:26 ` mark at klomp dot org

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-27440-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).