From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, palmer@sifive.com
Subject: Re: [PATCH] gdb: Initial baremetal riscv support
Date: Tue, 13 Feb 2018 19:49:00 -0000 [thread overview]
Message-ID: <83lgfwy8jy.fsf@gnu.org> (raw)
In-Reply-To: <20180213191455.2405-1-andrew.burgess@embecosm.com> (message from Andrew Burgess on Tue, 13 Feb 2018 19:14:55 +0000)
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: palmer@sifive.com, Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Tue, 13 Feb 2018 19:14:55 +0000
>
> This patch adds initial RiscV support to GDB.
Thanks.
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 1767cef920a..a3ba034674b 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -6,6 +6,8 @@
> * 'info proc' now works on running processes on FreeBSD systems and core
> files created on FreeBSD systems.
>
> +* Support for baremetal RiscV targets has been added.
> +
I think this should under "New targets".
next prev parent reply other threads:[~2018-02-13 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 19:15 Andrew Burgess
2018-02-13 19:49 ` Eli Zaretskii [this message]
2018-02-19 20:01 ` Simon Marchi
2018-02-27 1:09 ` [PATCHv2] " Andrew Burgess
2018-02-27 3:33 ` Simon Marchi
2018-03-02 20:09 ` [PATCHv3 0/2] Initial RiscV Support Andrew Burgess
2018-03-02 20:10 ` [PATCHv3 2/2] gdb: Initial baremetal riscv support Andrew Burgess
2018-03-03 6:27 ` Simon Marchi
2018-03-05 10:46 ` [PATCHv4 " Andrew Burgess
2018-03-05 22:35 ` Simon Marchi
2018-03-06 11:06 ` Yao Qi
2018-03-06 11:35 ` Yao Qi
2018-03-03 7:40 ` [PATCHv3 " Eli Zaretskii
2018-03-02 20:10 ` [PATCHv3 1/2] gdb/amd64: Ignore zero sized fields when calling functions Andrew Burgess
2018-03-03 6:29 ` Simon Marchi
2018-02-27 3:37 ` [PATCHv2] gdb: Initial baremetal riscv support Simon Marchi
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=83lgfwy8jy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palmer@sifive.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).