From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Cc: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: [PATCH 0/2] Fixes for some s390 fails with store.exp
Date: Fri, 15 Apr 2016 10:42:00 -0000 [thread overview]
Message-ID: <1460716939-27850-1-git-send-email-arnez@linux.vnet.ibm.com> (raw)
Since vector register support was added to GDB, store.exp shows some
FAILs on a z13. These are due to two different problems, each addressed
by a patch in this series.
Andreas Arnez (2):
S390: Take value from sub-register if applicable
Involve gdbarch in taking DWARF register pieces
gdb/dwarf2loc.c | 31 ++++++++++++++-----------------
gdb/findvar.c | 40 +++++++++++++++++++---------------------
gdb/gdbarch.c | 28 ++++++++++++++--------------
gdb/gdbarch.h | 15 +++++++--------
gdb/gdbarch.sh | 10 +++++-----
gdb/s390-linux-tdep.c | 27 ++++++++++++++-------------
gdb/spu-tdep.c | 20 ++++++--------------
gdb/value.h | 6 ++----
8 files changed, 81 insertions(+), 96 deletions(-)
--
2.5.0
next reply other threads:[~2016-04-15 10:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 10:42 Andreas Arnez [this message]
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 ` [PING][PATCH " Andreas Arnez
2016-04-28 14:47 ` 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=1460716939-27850-1-git-send-email-arnez@linux.vnet.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=Ulrich.Weigand@de.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