From: Pedro Alves <palves@redhat.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, qiyaoltc@gmail.com
Cc: Andrew Waterman <andrew@sifive.com>,
gdb-patches@sourceware.org, amodra@gmail.com
Subject: Re: [PATCH 1/2] RISC-V GDB Port
Date: Wed, 16 Nov 2016 19:36:00 -0000 [thread overview]
Message-ID: <f1b3fd57-2e1c-0aa2-198f-98771c9e132d@redhat.com> (raw)
In-Reply-To: <mhng-2585e691-2d32-42d8-9527-6f71a85ba5a6@palmer-mbp2014>
On 11/14/2016 10:39 PM, Palmer Dabbelt wrote:
>>> >> +
>>> >> + /* Check any target description for validity. */
>>> >> + if (tdesc_has_registers (info.target_desc))
>>> >> + {
>> >
>> > We don't have riscv target description yet.
> Yes. I'm amenable to adding one, but I'm not sure how.
>
You should really add them. Take a look at the ARC port,
which was recently added:
https://sourceware.org/ml/gdb-patches/2016-09/msg00248.html
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-11-16 19:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2016-11-16 19:40 ` Palmer Dabbelt
2016-11-16 19:48 ` Pedro Alves
2016-11-16 21:40 ` Yao Qi
2016-10-22 23:40 ` [PATCH 2/2] RISC-V GDB Simulator Port Palmer Dabbelt
2016-11-01 20:52 ` GDB port for RISC-V Palmer Dabbelt
2016-11-16 19:17 ` Palmer Dabbelt
2016-11-16 19:17 ` [PATCH 3/3] Add a RISC-V GDB NEWS entry Palmer Dabbelt
2016-11-16 19:41 ` Eli Zaretskii
2016-11-16 19:45 ` Palmer Dabbelt
2016-11-16 19:17 ` [PATCH 2/3] RISC-V GDB Port Palmer Dabbelt
2016-11-16 19:17 ` [PATCH 1/3] RISC-V Sim Port Palmer Dabbelt
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
2017-04-24 16:12 ` Palmer Dabbelt
2017-04-05 9: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=f1b3fd57-2e1c-0aa2-198f-98771c9e132d@redhat.com \
--to=palves@redhat.com \
--cc=amodra@gmail.com \
--cc=andrew@sifive.com \
--cc=gdb-patches@sourceware.org \
--cc=palmer@dabbelt.com \
--cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).