From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/9] Various DWARF piece fixes
Date: Fri, 07 Apr 2017 17:39:00 -0000 [thread overview]
Message-ID: <1491586736-21296-1-git-send-email-arnez@linux.vnet.ibm.com> (raw)
This patch series follows up on the proposed fix for PR21226:
https://sourceware.org/ml/gdb-patches/2017-03/msg00110.html
The fix for that issue is now provided by patch #3. More fixes for
various other DWARF piece handling issues are provided by patches #2, #5,
#6, and #8. Patch #1 establishes a new test case that is extended by some
of the other patches. Patches #4, #7, and #9 perform some clean-up.
Andreas Arnez (9):
Add test for modifiable DWARF locations
Fix size capping in write_pieced_value
PR gdb/21226: Take DWARF stack value pieces from LSB end
Remove addr_size field from struct piece_closure
Fix issues in write_pieced_value when targeting bit-fields
Fix handling of DWARF register pieces on big-endian targets
Improve logic for buffer allocation in read/write_pieced_value
Respect piece offset for DW_OP_bit_piece
Remove unnecessary copies of variables in read/write_pieced_value
gdb/dwarf2loc.c | 294 +++++++++++++--------------
gdb/testsuite/gdb.dwarf2/nonvar-access.exp | 21 +-
gdb/testsuite/gdb.dwarf2/var-access.c | 25 +++
gdb/testsuite/gdb.dwarf2/var-access.exp | 315 +++++++++++++++++++++++++++++
gdb/testsuite/lib/gdb-utils.exp | 2 +-
5 files changed, 503 insertions(+), 154 deletions(-)
create mode 100644 gdb/testsuite/gdb.dwarf2/var-access.c
create mode 100644 gdb/testsuite/gdb.dwarf2/var-access.exp
--
2.3.0
next reply other threads:[~2017-04-07 17:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 17:39 Andreas Arnez [this message]
2017-04-07 17:39 ` [PATCH 1/9] Add test for modifiable DWARF locations Andreas Arnez
2017-04-13 4:00 ` Simon Marchi
2017-04-13 10:52 ` Andreas Arnez
2017-04-13 8:36 ` Yao Qi
2017-04-13 11:46 ` Andreas Arnez
2017-04-07 17:40 ` [PATCH 2/9] Fix size capping in write_pieced_value Andreas Arnez
2017-04-13 8:18 ` Yao Qi
2017-04-13 16:35 ` Andreas Arnez
2017-04-19 9:15 ` Yao Qi
2017-04-19 14:36 ` Andreas Arnez
2017-04-19 15:00 ` Yao Qi
2017-04-07 17:41 ` [PATCH 4/9] Remove addr_size field from struct piece_closure Andreas Arnez
2017-04-13 9:10 ` Yao Qi
2017-04-14 3:39 ` Simon Marchi
2017-04-18 17:25 ` Andreas Arnez
2017-04-18 18:49 ` Simon Marchi
2017-04-07 17:41 ` [PATCH 3/9] PR gdb/21226: Take DWARF stack value pieces from LSB end Andreas Arnez
2017-04-14 3:36 ` Simon Marchi
2017-04-18 16:32 ` Andreas Arnez
2017-04-18 16:43 ` Simon Marchi
2017-04-07 17:42 ` [PATCH 5/9] Fix issues in write_pieced_value when targeting bit-fields Andreas Arnez
2017-04-14 5:18 ` Simon Marchi
2017-04-27 17:54 ` Andreas Arnez
2017-05-03 13:59 ` Simon Marchi
2017-04-07 17:43 ` [PATCH 7/9] Improve logic for buffer allocation in read/write_pieced_value Andreas Arnez
2017-04-14 14:51 ` Simon Marchi
2017-04-07 17:43 ` [PATCH 6/9] Fix handling of DWARF register pieces on big-endian targets Andreas Arnez
2017-04-14 14:11 ` Simon Marchi
2017-04-19 18:03 ` Andreas Arnez
2017-04-07 17:44 ` [PATCH 8/9] Respect piece offset for DW_OP_bit_piece Andreas Arnez
2017-04-14 15:07 ` Simon Marchi
2017-04-07 17:45 ` [PATCH 9/9] Remove unnecessary copies of variables in read/write_pieced_value Andreas Arnez
2017-04-14 15:21 ` Simon Marchi
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=1491586736-21296-1-git-send-email-arnez@linux.vnet.ibm.com \
--to=arnez@linux.vnet.ibm.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