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] [dwz, dwarf5] Add --dwarf-5 flag to generate .debug_sup, ref_sup and strp_sup
Date: Fri, 26 Feb 2021 23:26:28 +0000	[thread overview]
Message-ID: <bug-27440-11298-MhdNIiqe8U@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27440-11298@http.sourceware.org/bugzilla/>

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
commit 4e55da9f7700dda5936c7a486651674dbc782a7e
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sat Feb 20 10:47:53 2021 +0100

    PR27440 - add --dwarf-5 support

    This adds --dwarf-5 support, so that dwz can emit standard DWARF 5
    Supplementary object files with .debug_sup section and debug info referring
    to those with .debug_sup section instead of .gnu.debugaltlink and standard
    DWARF 5 DW_FORM_*sup instead of the DW_FORM_GNU_*alt forms.

            * dwz.1: Document --dwarf-5 and -5 options.
            * dwz.c (enum debug_section_kind): Add DEBUG_SUP.
            (debug_sections): Add .debug_sup section entry.
            (multifile_name, multifile_relative): Adjust comment.
            (dwarf_5): New variable.
            (note_strp_offset2): Adjust function comment.  If dwarf_5, return
            DW_FORM_strp_sup instead of DW_FORM_GNU_strp_alt.
            (macro_eq, read_macro, optimize_write_macro, handle_macro): Use
            standard DWARF 5 DW_MACRO_* names instead of their DW_MACRO_GNU_*
            aliases.
            (write_macro): Likewise.  Handle DW_FORM_strp_sup.
            (build_abbrevs_for_die): If dwarf_5, use DW_FORM_ref_sup4 instead
of
            DW_FORM_GNU_ref_alt.
            (write_unit_die): Handle DW_FORM_strp_sup.
            (write_die): Handle DW_FORM_ref_sup4 and DW_FORM_strp_sup.
            (read_dwarf): Fail if .debug_sup section is present, unless
            rd_multifile in dwarf_5 mode.
            (dwz): Write .debug_sup section instead of .gnu.debugaltlink if
            dwarf_5.
            (optimize_multifile): Write .debug_sup section instead of
            .note.gnu.build-id.
            (dwz_options): Add --dwarf-5 and -5 options.
            (dwz_multi_file_options_help): Mention .debug_sup section in -M
            description.  Add --dwarf-5 description.
            (main): Handle --dwarf-5 and -5 options.

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

      parent reply	other threads:[~2021-02-26 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 11:43 [Bug default/27440] New: " mark at klomp dot org
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 [this message]

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-MhdNIiqe8U@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).