From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/2, V2] Detect 64-bit-ness in PowerPC Book III-E
Date: Sun, 11 Jan 2015 08:27:00 -0000 [thread overview]
Message-ID: <1420964846-18881-1-git-send-email-yao@codesourcery.com> (raw)
In-Reply-To: <201412191549.sBJFnfPW030448@d03av02.boulder.ibm.com>
This patch is the V2 of https://sourceware.org/ml/gdb-patches/2014-12/msg00239.html
In V2, we check the different bit of register MSR on Book III-E and
Book III-S. In order to differentiate Book III-E and Book III-S, we
check the PPC_FEATURE_BOOKE from host's HWCAP, as Ulrich suggested.
Patch 1 is to move common macros into nat/ppc-linux.h, and patch 2
is the major part of this series.
Regression tested on powerpc-linux with GDBserver. Native powerpc
gdb isn't tested. Is it OK?
*** BLURB HERE ***
Yao Qi (2):
Move some ppc macros to nat/ppc-linux.h
Detect 64-bit-ness in PowerPC Book III-E
gdb/Makefile.in | 6 ++-
gdb/config/powerpc/ppc64-linux.mh | 2 +-
gdb/gdbserver/Makefile.in | 5 ++-
gdb/gdbserver/configure.srv | 2 +-
gdb/gdbserver/linux-ppc-low.c | 34 +--------------
gdb/nat/ppc-linux.c | 69 ++++++++++++++++++++++++++++++
gdb/nat/ppc-linux.h | 88 +++++++++++++++++++++++++++++++++++++++
gdb/ppc-linux-nat.c | 54 +-----------------------
8 files changed, 172 insertions(+), 88 deletions(-)
create mode 100644 gdb/nat/ppc-linux.c
create mode 100644 gdb/nat/ppc-linux.h
--
1.9.3
next prev parent reply other threads:[~2015-01-11 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 11:15 [PATCH] " Yao Qi
2014-12-11 15:31 ` Ulrich Weigand
2014-12-19 8:06 ` Yao Qi
2014-12-19 15:49 ` Ulrich Weigand
2015-01-11 8:27 ` Yao Qi [this message]
2015-01-11 8:27 ` [PATCH 1/2] Move some ppc macros to nat/ppc-linux.h Yao Qi
2015-01-13 16:57 ` Ulrich Weigand
2015-01-11 8:27 ` [PATCH 2/2] Detect 64-bit-ness in PowerPC Book III-E Yao Qi
2015-01-13 17:00 ` Ulrich Weigand
2015-01-14 2:54 ` Yao Qi
2015-01-14 12:47 ` Ulrich Weigand
2015-01-14 14:22 ` Yao Qi
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=1420964846-18881-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.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).