From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] gdbarch software_single_step returns VEC (CORE_ADDR) *
Date: Wed, 23 Mar 2016 14:10:00 -0000 [thread overview]
Message-ID: <1458742206-622-1-git-send-email-yao.qi@linaro.org> (raw)
This is a step toward changing gdbarch software_single_step to
"F:VEC (CORE_ADDR) *:software_single_step:struct regcache *regcache:regcache"
as I mentioned https://sourceware.org/ml/gdb-patches/2015-11/msg00591.html
It isn't trivial to replace frame_info with regcache because it may
break the target that frames have different gdbarch, such as spu, so
I still think about it. In the mean time, I post this series, to let
software_single_step returns VEC (CORE_ADDR) *, and
displaced_step_hw_singlestep can be removed (in patch 2).
The whole series are tested on {x86_64, ppc64p7, arm, aarch64}-linux.
*** BLURB HERE ***
Yao Qi (2):
gdbarch software_single_step returns VEC (CORE_ADDR) *
Remove gdbarch method displaced_step_hw_singlestep
gdb/aarch64-linux-tdep.c | 2 --
gdb/aarch64-tdep.c | 27 ++++++++--------------
gdb/alpha-tdep.c | 28 +++++++++++------------
gdb/alpha-tdep.h | 2 +-
gdb/arch-utils.c | 7 ------
gdb/arch-utils.h | 5 -----
gdb/arm-linux-tdep.c | 14 ++++--------
gdb/arm-tdep.c | 18 ++++++---------
gdb/arm-tdep.h | 4 +---
gdb/cris-tdep.c | 13 ++++++-----
gdb/gdbarch.c | 48 +++++++++++++++++++--------------------
gdb/gdbarch.h | 26 +++++++---------------
gdb/gdbarch.sh | 19 +++++-----------
gdb/infrun.c | 44 +++++++++++++++++++++++++++++++-----
gdb/mips-tdep.c | 58 ++++++++++++++++++++++++------------------------
gdb/mips-tdep.h | 2 +-
gdb/moxie-tdep.c | 34 +++++++++++++---------------
gdb/nios2-tdep.c | 8 +++----
gdb/ppc-tdep.h | 2 +-
gdb/record-full.c | 46 +++++++++++++++++++++++++++++++++-----
gdb/rs6000-aix-tdep.c | 12 +++++-----
gdb/rs6000-tdep.c | 24 ++++++--------------
gdb/s390-linux-tdep.c | 25 +++++++--------------
gdb/sparc-tdep.c | 9 ++++----
gdb/spu-tdep.c | 13 +++++------
gdb/tic6x-tdep.c | 9 ++++----
26 files changed, 246 insertions(+), 253 deletions(-)
--
1.9.1
next reply other threads:[~2016-03-23 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 14:10 Yao Qi [this message]
2016-03-23 14:10 ` [PATCH 2/2] Remove gdbarch method displaced_step_hw_singlestep Yao Qi
2016-03-23 17:26 ` Pedro Alves
2016-05-09 11:05 ` Yao Qi
2016-03-23 14:10 ` [PATCH 1/2] gdbarch software_single_step returns VEC (CORE_ADDR) * Yao Qi
2016-03-23 17:25 ` Pedro Alves
2016-03-30 14:14 ` Yao Qi
2016-04-27 15:19 ` Pedro Alves
2016-04-29 14:48 ` Yao Qi
2016-05-02 10:21 ` Pedro Alves
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=1458742206-622-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).