Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org, nd@arm.com
Subject: Re: [PATCH] Add SVE to NEWS and GDB manual
Date: Tue, 21 Aug 2018 17:58:00 -0000	[thread overview]
Message-ID: <83bm9vd2k2.fsf@gnu.org> (raw)
In-Reply-To: <2DF2CE84-B4A6-4289-88A9-E36061B2D4A4@arm.com> (message from Alan	Hayward on Tue, 21 Aug 2018 17:29:18 +0000)

> From: Alan Hayward <Alan.Hayward@arm.com>
> CC: GDB Patches <gdb-patches@sourceware.org>, nd <nd@arm.com>
> Date: Tue, 21 Aug 2018 17:29:18 +0000
> 
> Updated version below.
> This version ok?
> 
> 
> 
> 2018-08-21  Alan Hayward  <alan.hayward@arm.com>
> 
> gdb/
> 	* NEWS: Add SVE to 8.2 section.
> 	* doc/gdb.texinfo: Add SVE to AArch64 section.

The gdb.texinfo entry should mention the node in which the changes are
made, as if it were a function.

> +When @value{GDBN} is debugging the AArch64 architecture, if the Scalable Vector
> +Extension (SVE) is present then @value{GDBN} will provide the vector registers
                             ^
Comma missing there.

> +@code{$z0} through @code{$z31}, vector predicate registers @code{$p0} through
> +@code{$p15}, and the @code{$ffr} register.  In addition the pseudo register
                                                          ^
And another.

OK with those gotchas fixed.

Thanks.


      reply	other threads:[~2018-08-21 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 12:53 Alan Hayward
2018-08-21 14:36 ` Pedro Alves
2018-08-21 17:29   ` Alan Hayward
2018-08-21 17:58     ` Eli Zaretskii [this message]

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=83bm9vd2k2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=palves@redhat.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