Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org,  ccoutant@google.com
Subject: Re: [PATCH 0/6] DWARF Two Level Line Tables
Date: Fri, 13 Mar 2015 17:32:00 -0000	[thread overview]
Message-ID: <86egoshkg9.fsf@gmail.com> (raw)
In-Reply-To: <yjt2egou7zsx.fsf@ruffy.mtv.corp.google.com> (Doug Evans's	message of "Thu, 12 Mar 2015 12:58:54 -0700")

Doug Evans <dje@google.com> writes:

> This patch set adds Two Level Line Tables support to gdb,
> as well as support for the DWARF 5 line table extensions.

Hi Doug,
I notice that a lot of code is added into dwarf2read.c in this patch
set.  Is it possible to put them in a separated file or split
dwarf2read.c?  Every time, when I read dwarf2read.c, I find it is too
long to understand.  IWBN to split dwarf2read.c, at least, add new stuff
into a new file.

-- 
Yao (齐尧)


  reply	other threads:[~2015-03-13 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 19:59 Doug Evans
2015-03-13 17:32 ` Yao Qi [this message]
2015-03-13 17:44   ` Doug Evans
2015-05-28 17:12 ` Doug Evans

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=86egoshkg9.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=ccoutant@google.com \
    --cc=dje@google.com \
    --cc=gdb-patches@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