public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH v2 1/3] gdb/dwarf2: move some things to read.h
Date: Wed, 15 Feb 2023 15:12:27 -0500	[thread overview]
Message-ID: <e5b7e815-1b7e-d893-ed1e-e079338de901@polymtl.ca> (raw)
In-Reply-To: <87bklwrmy0.fsf@tromey.com>

On 2/14/23 15:50, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Simon> From: Simon Marchi <simon.marchi@polymtl.ca>
> Simon> New in v2:
> 
> Simon>  - do not move offset_view
> Simon>  - move read_addrmap_from_aranges and create_cu_from_index_list in this
> Simon>    patch, instead of in subsequent patches
> Simon>  - fix formatting of declarations, add extern keyword
> 
> Simon> The following 2 patches move .gdb_index and .debug_names reading code to
> Simon> their own file.  Prepare this by exposing some things used by that code
> Simon> to read.h.
> 
> Thank you.
> Approved-By: Tom Tromey <tom@tromey.com>
> 
> Tom

Thanks, I will push the series.

Simon

      reply	other threads:[~2023-02-15 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 19:55 Simon Marchi
2023-02-14 19:55 ` [PATCH v2 2/3] gdb/dwarf2: split .gdb_index reading code to own file Simon Marchi
2023-02-14 19:55 ` [PATCH v2 3/3] gdb/dwarf2: split .debug_names " Simon Marchi
2023-02-14 20:50 ` [PATCH v2 1/3] gdb/dwarf2: move some things to read.h Tom Tromey
2023-02-15 20:12   ` Simon Marchi [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=e5b7e815-1b7e-d893-ed1e-e079338de901@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.com \
    --cc=tom@tromey.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).