From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/7 v2] Class-fy partial_die_info
Date: Thu, 22 Feb 2018 15:36:00 -0000 [thread overview]
Message-ID: <1519313796-2397-1-git-send-email-yao.qi@linaro.org> (raw)
When I fix some issues related to dwarf, I class-fy partial_die_info as
part of the fix. The class-fication bits can go upstream first.
This is the v2 of this patch series, v1 can be found
https://sourceware.org/ml/gdb-patches/2018-01/msg00505.html Changes
in v2 are,
- Don't move the location of partial_die_info::fixup_called, as it may
increase the memory usage,
- Add some comments to read_partial_die,
*** BLURB HERE ***
Yao Qi (7):
Re-write partial_die_info allocation in load_partial_dies
Don't check abbrev is NULL in read_partial_die
Change find_partial_die_in_comp_unit to dwarf2_cu::find_partial_die
Class-fy partial_die_info
Remove one argument abbrev_len in read_partial_die
Move fixup_partial_die to partial_die_info::fixup
Move read_partial_die to partial_die_info::read
gdb/dwarf2read.c | 337 ++++++++++++++++++++++++++++++-------------------------
1 file changed, 183 insertions(+), 154 deletions(-)
--
1.9.1
next reply other threads:[~2018-02-22 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 15:36 Yao Qi [this message]
2018-02-22 15:36 ` [PATCH 1/7] Re-write partial_die_info allocation in load_partial_dies Yao Qi
2018-02-22 15:36 ` [PATCH 3/7] Change find_partial_die_in_comp_unit to dwarf2_cu::find_partial_die Yao Qi
2018-02-22 15:36 ` [PATCH 5/7] Remove one argument abbrev_len in read_partial_die Yao Qi
2018-02-22 15:36 ` [PATCH 4/7] Class-fy partial_die_info Yao Qi
2018-02-22 15:36 ` [PATCH 6/7] Move fixup_partial_die to partial_die_info::fixup Yao Qi
2018-02-22 15:36 ` [PATCH 2/7] Don't check abbrev is NULL in read_partial_die Yao Qi
2018-02-25 23:33 ` Simon Marchi
2018-02-22 15:36 ` [PATCH 7/7] Move read_partial_die to partial_die_info::read Yao Qi
2018-02-25 23:52 ` [PATCH 0/7 v2] Class-fy partial_die_info Simon Marchi
2018-02-26 15:39 ` Yao Qi
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=1519313796-2397-1-git-send-email-yao.qi@linaro.org \
--to=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).