From: Yao Qi <qiyaoltc@gmail.com>
To: Ivo Raisr <ivo.raisr@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Bug 20936 - provide sparc and sparcv9 target description XML files
Date: Wed, 25 Jan 2017 22:42:00 -0000 [thread overview]
Message-ID: <20170125224241.twkvdrqzlfe6s7fe@localhost> (raw)
In-Reply-To: <6cfe328e-9928-5060-a5ab-e984219e1c81@oracle.com>
On 17-01-17 22:37:59, Ivo Raisr wrote:
> diff -Nupr a/gdb/doc/gdb.texinfo gdb-7.11/gdb/doc/gdb.texinfo
> --- a/gdb/doc/gdb.texinfo 2016-02-24 01:55:15.000000000 +0000
> +++ gdb-7.11/gdb/doc/gdb.texinfo 2017-01-17 04:51:21.533190029 +0000
> @@ -40658,6 +40658,7 @@ registers using the capitalization used
> * Nios II Features::
> * PowerPC Features::
> * S/390 and System z Features::
> +* Sparc Features::
> * TIC6x Features::
> @end menu
>
> @@ -40945,6 +40946,48 @@ through @samp{f15} to present the 128-bi
> contain the 128-bit wide vector registers @samp{v16} through
> @samp{v31}.
>
> +@node Sparc Features
> +@subsection Sparc Features
> +@cindex target descriptions, sparc32 features
> +@cindex target descriptions, sparc64 features
> +The @samp{org.gnu.gdb.sparc.cpu} feature is required for sparc32/sparc64
> +targets. It should describe the following registers:
> +
> +@itemize @minus
> +@item
> +@samp{g0} through @samp{g7}
> +@item
> +@samp{o0} through @samp{o7}
> +@item
> +@samp{l0} through @samp{l7}
> +@item
> +@samp{i0} through @samp{i7}
> +@end itemize
> +
> +They may be 32-bit or 64-bit depending on the target.
> +
> +Also the @samp{org.gnu.gdb.sparc.fpu} feature is required for sparc32/sparc64
> +targets. It should describe the following registers:
> +
> +@itemize @minus
> +@item
> +@samp{f0} through @samp{f31}
> +@item
> +@samp{f32} through @samp{f62} for sparc64
> +@end itemize
> +
> +The @samp{org.gnu.gdb.sparc.cp0} feature is required for sparc32/sparc64
> +targets. It should describe the following registers:
> +
> +@itemize @minus
> +@item
> +@samp{y}, @samp{psr}, @samp{wim}, @samp{tbr}, @samp{pc}, @samp{npc},
> +@samp{fsr}, and @samp{csr} for sparc32
> +@item
> +@samp{pc}, @samp{npc}, @samp{state}, @samp{fsr}, @samp{fprs}, and @samp{y}
> +for sparc64
> +@end itemize
> +
> @node TIC6x Features
> @subsection TMS320C6x Features
> @cindex target descriptions, TIC6x features
If the doc hasn't been reviewed before, it needs a doc review.
> diff -Nupr a/gdb/features/sparc/sparc32-cp0.xml gdb-7.11/gdb/features/sparc/sparc32-cp0.xml
> --- a/gdb/features/sparc/sparc32-cp0.xml 1969-12-31 16:00:00.000000000 +0000
> +++ gdb-7.11/gdb/features/sparc/sparc32-cp0.xml 2017-01-17 04:51:21.534235184 +0000
> @@ -0,0 +1,19 @@
> +<?xml version="1.0"?>
> +<!-- Copyright (C) 2013-2016 Free Software Foundation, Inc.
Why does the year range start from 2013? It should end on 2017, anyway.
> +
> + Copying and distribution of this file, with or without modification,
> + are permitted in any medium without royalty provided the copyright
> + notice and this notice are preserved. -->
> +
non-doc bits of this patch look good to me.
--
Yao
next prev parent reply other threads:[~2017-01-25 22:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 11:41 Ivo Raisr
2016-12-06 15:26 ` Yao Qi
2016-12-06 23:46 ` Ivo Raisr
2016-12-06 23:58 ` Ivo Raisr
2016-12-12 12:54 ` Yao Qi
2017-01-04 17:43 ` Ivo Raisr
2017-01-05 14:31 ` Yao Qi
2017-01-06 15:12 ` Ivo Raisr
2017-01-09 17:35 ` Yao Qi
2017-01-09 21:18 ` Ivo Raisr
2017-01-10 9:29 ` Yao Qi
2017-01-11 13:15 ` Ivo Raisr
2017-01-11 15:46 ` Yao Qi
2017-01-12 11:09 ` Ivo Raisr
2017-01-16 16:50 ` Jose E. Marchesi
2017-01-25 15:46 ` Pedro Alves
2017-01-25 16:05 ` Ivo Raisr
2017-01-25 16:24 ` Pedro Alves
2017-01-25 16:26 ` Ivo Raisr
2017-01-25 16:44 ` Yao Qi
2017-01-17 21:38 ` Ivo Raisr
2017-01-25 5:46 ` Ivo Raisr
2017-01-25 22:42 ` Yao Qi [this message]
2017-01-26 11:23 ` Ivo Raisr
2016-12-11 17:23 ` Ivo Raisr
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=20170125224241.twkvdrqzlfe6s7fe@localhost \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=ivo.raisr@oracle.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