public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: jimw@sifive.com, gdb-patches@sourceware.org, palmer@sifive.com,
	jhb@freebsd.org
Subject: Re: [PATCH] gdb/riscv: Add target description support
Date: Wed, 21 Nov 2018 12:37:00 -0000	[thread overview]
Message-ID: <83y39mhain.fsf@gnu.org> (raw)
In-Reply-To: <20181121112335.GX16539@embecosm.com> (message from Andrew	Burgess on Wed, 21 Nov 2018 11:23:35 +0000)

> Date: Wed, 21 Nov 2018 11:23:35 +0000
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: gdb-patches@sourceware.org, Palmer Dabbelt <palmer@sifive.com>,
> 	John Baldwin <jhb@freebsd.org>
> 
> Eli,
> 
> I believe I still need a doc review before I can merge this patch.
> Could I ask you to take a look please.

Sorry, I thought I already did.  See below.

> +The @samp{org.gnu.gdb.riscv.fpu} feature is optional.  If present it
                                                                    ^
Please insert a comma where shown.

> +should contain registers @samp{f0} through @samp{f31}, @samp{fflags},
> +@samp{frm}, and @samp{fcsr}.  As with the cpu feature either the
                                                        ^
And here.

> +The @samp{org.gnu.gdb.riscv.virtual} feature is optional.  If present
                                                                        ^
And here.

> +it should contain registers that are not backed by real registers on
> +the target but are instead virtual, where the register value is
             ^
And here.

> +derived from other target state.  In many ways these are like GDBs
                                                                 ^^^^
@value{GDBN}s

> +The @samp{org.gnu.gdb.riscv.csr} feature is optional.  If present it
                                                                    ^
Need a comma there.

OK with these nits fixed.

Thanks.

  reply	other threads:[~2018-11-21 12:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 16:08 [RFC] " Andrew Burgess
2018-11-08 18:33 ` John Baldwin
2018-11-08 19:32   ` Palmer Dabbelt
2018-11-08 19:41     ` John Baldwin
2018-11-14 14:29   ` Andrew Burgess
2018-11-14 17:42     ` John Baldwin
2018-11-08 21:57 ` Jim Wilson
2018-11-13 15:05   ` Andrew Burgess
2018-11-13 20:08 ` Pedro Alves
2018-11-14 14:58 ` [PATCH] " Andrew Burgess
2018-11-19  3:51   ` Jim Wilson
2018-11-21 11:23     ` Andrew Burgess
2018-11-21 12:37       ` Eli Zaretskii [this message]
2018-11-21 13:19         ` Andrew Burgess
2019-02-22 17:42   ` Tom Tromey
2019-02-22 19:24     ` Jim Wilson
2019-02-23 20:51       ` Andrew Burgess
2019-02-24  6:21         ` Jim Wilson
2019-02-26  5:02           ` Joel Brobecker
2019-02-26 17:26             ` Jim Wilson
2019-02-26 18:22               ` Andrew Burgess
2019-02-26 18:40                 ` Jim Wilson
2019-02-26 19:27                   ` Jim Wilson
2019-02-26 20:30                     ` Andrew Burgess
2019-02-23 20:40     ` Andrew Burgess
2019-02-26 11:55       ` Joel Brobecker
2019-03-04 16:18       ` Tom Tromey

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=83y39mhain.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@freebsd.org \
    --cc=jimw@sifive.com \
    --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).