From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [ping] [PATCH v2 00/19] Various DWARF piece fixes
Date: Tue, 30 May 2017 16:42:00 -0000 [thread overview]
Message-ID: <m337bmmh4c.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <1494352015-10465-1-git-send-email-arnez@linux.vnet.ibm.com> (Andreas Arnez's message of "Tue, 9 May 2017 19:45:56 +0200")
Ping:
https://sourceware.org/ml/gdb-patches/2017-05/msg00215.html
ON Tue, May 09 2017, Andreas Arnez wrote:
> This series fixes various issues with DWARF piece handling.
> Specifically it almost rewrites the functions read_pieced_value and
> write_pieced_value in multiple steps. Test cases are added as well.
So far I've received feedback from Yao, and for v1 also from Simon.
Thanks again for that! Now, if I tracked correctly, the patches
check-marked with [X] are approved:
- [X] Add test for modifiable DWARF locations
- [X] write_pieced_value: Fix size capping logic
- [X] PR gdb/21226: Take DWARF stack value pieces from LSB end
- [X] Remove addr_size field from struct piece_closure
- [X] gdb/testsuite: Add "get_endianness" convenience proc
- [X] read/write_pieced_value: Respect value parent's offset
- [X] write_pieced_value: Fix copy/paste error in size calculation
- [X] write_pieced_value: Include transfer size in byte-wise check
- [X] write_pieced_value: Fix buffer offset for memory pieces
- [X] write_pieced_value: Transfer least significant bits into bit-field
- [X] Add DWARF piece test cases for bit-field access
- [X] read/write_pieced_value: Drop 'buffer_size' variable
- [ ] Fix handling of DWARF register pieces on big-endian targets
- [ ] read/write_pieced_value: Improve logic for buffer allocation
- [X] Respect piece offset for DW_OP_bit_piece
- [ ] read/write_pieced_value: Remove unnecessary variable copies
- [ ] Fix bit-/byte-offset mismatch in parameter to read_value_memory
- [X] write_pieced_value: Notify memory_changed observers
- [ ] read/write_pieced_value: Merge into one function
For the 5 non-check-marked patches I haven't received feedback yet.
--
Andreas
next prev parent reply other threads:[~2017-05-30 16:42 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 17:47 Andreas Arnez
2017-05-09 17:47 ` [PATCH v2 01/19] Add test for modifiable DWARF locations Andreas Arnez
2017-05-11 21:22 ` Yao Qi
2017-05-09 17:48 ` [PATCH v2 02/19] write_pieced_value: Fix size capping logic Andreas Arnez
2017-05-11 21:26 ` Yao Qi
2017-05-09 17:49 ` [PATCH v2 04/19] Remove addr_size field from struct piece_closure Andreas Arnez
2017-05-11 21:29 ` Yao Qi
2017-05-09 17:49 ` [PATCH v2 03/19] PR gdb/21226: Take DWARF stack value pieces from LSB end Andreas Arnez
2017-05-15 9:32 ` Yao Qi
2017-05-15 16:35 ` Andreas Arnez
2017-05-16 7:53 ` Yao Qi
[not found] ` <m34lwlf2cq.fsf@oc1027705133.ibm.com>
2017-05-16 13:50 ` Yao Qi
2017-05-09 17:50 ` [PATCH v2 05/19] gdb/testsuite: Add "get_endianness" convenience proc Andreas Arnez
2017-05-11 21:32 ` Yao Qi
2017-05-09 17:51 ` [PATCH v2 07/19] write_pieced_value: Fix copy/paste error in size calculation Andreas Arnez
2017-05-16 8:29 ` Yao Qi
2017-05-09 17:51 ` [PATCH v2 06/19] read/write_pieced_value: Respect value parent's offset Andreas Arnez
2017-05-16 8:18 ` Yao Qi
2017-05-09 17:52 ` [PATCH v2 08/19] write_pieced_value: Include transfer size in byte-wise check Andreas Arnez
2017-05-16 8:32 ` Yao Qi
2017-05-16 13:45 ` Andreas Arnez
2017-05-09 17:53 ` [PATCH v2 09/19] write_pieced_value: Fix buffer offset for memory pieces Andreas Arnez
2017-05-16 8:46 ` Yao Qi
2017-05-09 17:53 ` [PATCH v2 10/19] write_pieced_value: Transfer least significant bits into bit-field Andreas Arnez
2017-05-16 9:14 ` Yao Qi
2017-05-09 17:54 ` [PATCH v2 11/19] Add DWARF piece test cases for bit-field access Andreas Arnez
2017-05-16 13:52 ` Yao Qi
2017-05-09 17:55 ` [PATCH v2 13/19] Fix handling of DWARF register pieces on big-endian targets Andreas Arnez
2017-06-12 13:12 ` Yao Qi
2017-05-09 17:55 ` [PATCH v2 12/19] read/write_pieced_value: Drop 'buffer_size' variable Andreas Arnez
2017-05-16 14:08 ` Yao Qi
2017-05-16 17:51 ` Andreas Arnez
2017-05-09 17:56 ` [PATCH v2 14/19] read/write_pieced_value: Improve logic for buffer allocation Andreas Arnez
2017-06-12 13:28 ` Yao Qi
2017-06-12 19:40 ` Simon Marchi
2017-06-13 12:10 ` Andreas Arnez
2017-06-13 12:18 ` Pedro Alves
2017-06-13 14:41 ` Andreas Arnez
2017-05-09 17:57 ` [PATCH v2 15/19] Respect piece offset for DW_OP_bit_piece Andreas Arnez
2017-05-16 21:08 ` Yao Qi
2017-05-09 17:58 ` [PATCH v2 16/19] read/write_pieced_value: Remove unnecessary variable copies Andreas Arnez
2017-06-12 13:50 ` Yao Qi
2017-05-09 17:58 ` [PATCH v2 17/19] Fix bit-/byte-offset mismatch in parameter to read_value_memory Andreas Arnez
2017-05-30 19:59 ` Simon Marchi
2017-05-31 14:02 ` Andreas Arnez
2017-05-31 14:30 ` Simon Marchi
2017-05-09 17:59 ` [PATCH v2 18/19] write_pieced_value: Notify memory_changed observers Andreas Arnez
2017-05-16 21:12 ` Yao Qi
2017-05-09 18:00 ` [PATCH v2 19/19] read/write_pieced_value: Merge into one function Andreas Arnez
2017-06-12 13:57 ` Yao Qi
2017-06-12 14:34 ` Andreas Arnez
2017-06-13 9:17 ` Yao Qi
2017-05-30 16:42 ` Andreas Arnez [this message]
2017-05-30 20:44 ` [PATCH v2 00/19] Various DWARF piece fixes Simon Marchi
2017-05-31 14:24 ` Andreas Arnez
2017-06-12 11:38 ` Andreas Arnez
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=m337bmmh4c.fsf@oc1027705133.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).