From: Yao Qi <qiyaoltc@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] RISC-V GDB Port
Date: Tue, 04 Apr 2017 21:48:00 -0000 [thread overview]
Message-ID: <86a87v6dzr.fsf@gmail.com> (raw)
In-Reply-To: <20170307043029.3672-2-palmer@dabbelt.com> (Palmer Dabbelt's message of "Mon, 6 Mar 2017 20:30:28 -0800")
Palmer Dabbelt <palmer@dabbelt.com> writes:
Hi,
I have some time today, so I can review the patch.
> gdb/Makefile.in | 5 +
> gdb/config/riscv/linux.mh | 30 +
> gdb/features/Makefile | 2 +
> gdb/features/riscv.c | 86 +++
> gdb/features/riscv.xml | 81 +++
> gdb/gdbserver/linux-riscv-low.c | 221 +++++++
> gdb/regformats/riscv.dat | 69 ++
> gdb/riscv-linux-nat.c | 77 +++
> gdb/riscv-linux-tdep.c | 80 +++
> gdb/riscv-linux-tdep.h | 30 +
> gdb/riscv-tdep.c | 1368 +++++++++++++++++++++++++++++++++++++++
> gdb/riscv-tdep.h | 96 +++
> include/gdb/sim-riscv.h | 98 +++
Before I read the patch further, my suggestion is to split your patch
to following parts next time,
- bare metal support, riscv-tdep.c
- linux target support, riscv-linux-tdep.c,
- linux host support, riscv-linux-nat.c,
- gdbserver support, gdbserver/linux-riscv-low.c
- target description,
I am surprised that there is no change to gdb/testsuite/.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-04-04 21:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 20:31 RISC-V GDB Port v3 Palmer Dabbelt
2017-03-06 20:31 ` [PATCH 1/2] RISC-V GDB Port Palmer Dabbelt
2017-04-04 21:48 ` Yao Qi [this message]
2017-04-24 16:12 ` Palmer Dabbelt
2017-04-05 9:22 ` Yao Qi
2017-03-06 20:31 ` [PATCH 2/2] RISC-V sim Port Palmer Dabbelt
2017-03-10 19:38 ` RISC-V GDB Port v3 Palmer Dabbelt
2017-03-21 9:23 ` Yao Qi
2017-03-21 16:04 ` Palmer Dabbelt
2017-04-05 9:30 ` Yao Qi
[not found] <1477179037-32066-1-git-send-email-palmer@dabbelt.com>
2016-10-22 23:40 ` GDB port for RISC-V Palmer Dabbelt
2016-10-22 23:40 ` [PATCH 1/2] RISC-V GDB Port Palmer Dabbelt
2016-11-03 12:39 ` Yao Qi
2016-11-14 22:39 ` Palmer Dabbelt
2016-11-16 19:36 ` Pedro Alves
2016-11-16 19:40 ` Palmer Dabbelt
2016-11-16 19:48 ` Pedro Alves
2016-11-16 21:40 ` 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=86a87v6dzr.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palmer@dabbelt.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