From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>, Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [PING][PATCH 2/2] Involve gdbarch in taking DWARF register pieces
Date: Thu, 28 Apr 2016 13:24:00 -0000 [thread overview]
Message-ID: <m3h9elvpc7.fsf_-_@oc1027705133.ibm.com> (raw)
In-Reply-To: <m3a8kpx0ls.fsf@oc1027705133.ibm.com> (Andreas Arnez's message of "Tue, 19 Apr 2016 14:08:15 +0200")
Ping:
https://sourceware.org/ml/gdb-patches/2016-04/msg00437.html
IIRC, there was some uncertainty about the clarity/meaning of the new
gdbarch method's description below. Or has this cleared up by now?
On Tue, Apr 19 2016, Andreas Arnez wrote:
> Here's another attempt:
>
> Determine the physical placement of a piece of size LEN within register
> *REGNUM, possibly overwriting *REGNUM. (E.g., some ABIs have unwindable
> sub-registers embedded in non-unwindable full registers, and this method
> diverts from the full register to the sub-register if possible.)
> Returns the byte offset of the data within the (possibly adjusted)
> register. This method is used for determining the placement of a
> LEN-sized DWARF piece (DW_OP_piece) and when interpreting a register as
> a LEN-sized type (unless convert_register_p indicates that the type
> needs a special conversion).
[...]
> gdb/ChangeLog:
>
> * gdbarch.sh (value_from_register): Remove.
> (register_piece_placement): New.
> * gdbarch.c: Regenerate.
> * gdbarch.h: Likewise.
> * dwarf2loc.c (read_pieced_value): Get arch-specific placement of
> a register piece from gdbarch_register_piece_placement.
> (write_pieced_value): Likewise.
> * value.h (default_value_from_register): Remove.
> (default_register_piece_placement): Declare.
> * findvar.c (default_value_from_register): Remove.
> (default_register_piece_placement): New.
> (value_from_register): Call gdbarch_register_piece_placement
> instead of gdbarch_value_from_register.
> (address_from_register): Likewise.
> * s390-linux-tdep.c (s390_value_from_register): Remove.
> (s390_register_piece_placement): New.
> (s390_gdbarch_init): Set new gdbarch method
> register_piece_placement instead of value_from_register.
> * spu-tdep.c (spu_value_from_register): Remove.
> (spu_register_piece_placement): New.
> (spu_gdbarch_init): Set new gdbarch method
> register_piece_placement instead of value_from_register.
next prev parent reply other threads:[~2016-04-28 13:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 10:42 [PATCH 0/2] Fixes for some s390 fails with store.exp Andreas Arnez
2016-04-15 10:43 ` [PATCH 1/2] S390: Take value from sub-register if applicable Andreas Arnez
2016-04-15 18:08 ` Ulrich Weigand
2016-04-15 10:43 ` [PATCH 2/2] Involve gdbarch in taking DWARF register pieces Andreas Arnez
2016-04-15 18:10 ` Ulrich Weigand
2016-04-15 18:37 ` Pedro Alves
2016-04-18 11:53 ` Andreas Arnez
2016-04-18 13:53 ` Pedro Alves
2016-04-18 15:02 ` Andreas Arnez
2016-04-18 15:55 ` Pedro Alves
2016-04-18 15:57 ` Doug Evans
2016-04-19 12:08 ` Andreas Arnez
2016-04-28 13:24 ` Andreas Arnez [this message]
2016-04-28 14:47 ` [PING][PATCH " Pedro Alves
2016-04-28 16:51 ` Andreas Arnez
2016-04-28 18:16 ` Andreas Arnez
2016-04-28 22:15 ` Pedro Alves
2016-04-28 22:15 ` Pedro Alves
2016-06-14 17:03 ` Jan Kratochvil
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=m3h9elvpc7.fsf_-_@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=uweigand@de.ibm.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