From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/3, V2] MIPS: Provide FPU info and decode FCSR in `info float'
Date: Wed, 17 Dec 2014 06:46:00 -0000 [thread overview]
Message-ID: <1418798765-23198-1-git-send-email-yao@codesourcery.com> (raw)
This patch series is the V2, to mainly address review comments in V1,
which can be found in https://sourceware.org/ml/gdb-patches/2012-05/msg00938.html
In the review to V1, Joel suggested to continue dumping float point
registers in 'info float' and we do that in V2 by calling
print_float_info's default implementation default_print_float_info.
During writing this patch, I find h8300_print_float_info isn't needed.
I remove it too.
This patch series is tested under mips-linux-gnu. Is it OK?
*** BLURB HERE ***
Yao Qi (3):
Remove h8300_print_float_info
Refactor gdbarch method print_float_info
MIPS: Provide FPU info and decode FCSR in `info float'
gdb/gdbarch.c | 13 +-----
gdb/gdbarch.h | 2 -
gdb/gdbarch.sh | 2 +-
gdb/h8300-tdep.c | 9 ----
gdb/infcmd.c | 45 ++++++++++---------
gdb/inferior.h | 5 +++
gdb/mips-tdep.c | 95 ++++++++++++++++++++++++++++++++++++++++
gdb/testsuite/gdb.base/float.exp | 9 +++-
8 files changed, 135 insertions(+), 45 deletions(-)
--
1.9.3
next reply other threads:[~2014-12-17 6:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 6:46 Yao Qi [this message]
2014-12-17 6:46 ` [PATCH 3/3] " Yao Qi
2014-12-17 10:53 ` Pedro Alves
2014-12-17 12:40 ` Yao Qi
2014-12-18 1:07 ` Yao Qi
2014-12-18 11:16 ` Pedro Alves
2014-12-21 0:14 ` Maciej W. Rozycki
2014-12-17 6:46 ` [PATCH 1/3] Remove h8300_print_float_info Yao Qi
2014-12-17 6:46 ` [PATCH 2/3] Refactor gdbarch method print_float_info Yao Qi
2014-12-17 13:24 ` Pedro Alves
2014-12-18 1:02 ` Yao Qi
2014-12-18 11:14 ` Pedro Alves
2014-12-18 12:52 ` [PATCH 0/3, V2] MIPS: Provide FPU info and decode FCSR in `info float' 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=1418798765-23198-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).