public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [binutils patch] DWARF-5: Extend bfd/dwarf2.c parse_comp_unit()
Date: Tue, 04 Jul 2017 04:04:00 -0000	[thread overview]
Message-ID: <20170704040325.GC14520@bubble.grove.modra.org> (raw)
In-Reply-To: <20170701105702.GA31016@host1.jankratochvil.net>

On Sat, Jul 01, 2017 at 12:57:02PM +0200, Jan Kratochvil wrote:
> 2017-07-01  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* dwarf2.c (struct dwarf2_debug): Add fields dwarf_line_str_buffer and
> 	dwarf_line_str_size.
> 	(struct attr_abbrev): Add field implicit_const.
> 	(dwarf_debug_sections): Add .debug_line_str.
> 	(enum dwarf_debug_section_enum): Add debug_line_str and debug_max.
> 	(dwarf_debug_section_assert): Add static assertion.
> 	(read_indirect_line_string): New.
> 	(read_abbrevs): Support DW_FORM_implicit_const.
> 	(is_str_attr): Support DW_FORM_line_strp.
> 	(read_attribute_value): Support DW_FORM_line_strp and
> 	DW_FORM_implicit_const.
> 	(read_attribute): Support DW_FORM_implicit_const.
> 	(line_info_add_include_dir, line_info_add_include_dir_stub):
> 	(line_info_add_file_name, read_formatted_entries): New.
> 	(decode_line_info, parse_comp_unit): Support DWARF 5.
> 	(_bfd_dwarf2_cleanup_debug_info): Free dwarf_line_str_buffer.

OK.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2017-07-04  4:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01 10:57 Jan Kratochvil
2017-07-04  4:04 ` Alan Modra [this message]
2017-07-04  8:10   ` [binutils commit] " Jan Kratochvil
2017-07-05 16:07     ` H.J. Lu

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=20170704040325.GC14520@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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).