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: Tue, 06 Dec 2016 15:26:00 -0000 [thread overview]
Message-ID: <20161206152616.GC28789@E107787-LIN> (raw)
In-Reply-To: <46200a1e-29f7-8e20-c0b5-3f6f25c82d45@oracle.com>
On 16-12-06 11:40:42, Ivo Raisr wrote:
> Please find attached a patch which fixes PR tdep/20936.
>
> This patch provides sparc (32-bit) and sparcv9 (64-bit) target
> description XML files.
> Files sparc{64}-cp0.xml, sparc{64}-cpu.xml and sparc{64}-fpu.xml are
> OS independent.
> Files sparc-solaris.xml and sparc64-solaris.xml are specific to Solaris.
Hi Ivo,
Could you add a new directory "sparc" in gdb/features/ and put all
.xml files there?
>
> gdb regression test suite was run successfully on Solaris/sparc.
>
> This PR with a patch is used as a foundation for another patch which
> will enhance sparc{64}-tdep
> with the ability to work the Valgrind shadow registers. Stay tuned.
>
I suppose your next patch is to change sparc{64}-tdep.c to use these
target descriptions. I'd like to get target description definition
and use in a single patch. You add some thing new in this patch,
but it is not used at all.
All these new added features should be documented
https://sourceware.org/gdb/current/onlinedocs/gdb/Standard-Target-Features.html
>
> ChangeLog entry:
> 2016-12-06 Ivo Raisr <ivo.raisr@oracle.com>
>
> PR tdep/20936
> Provide sparc and sparcv9 target description XML files.
Indented by tab rather than spaces.
> * sparc-cp0.xml, sparc-cpu.xml, sparc-fpu.xml: New files for
> sparc 32-bit.
> * sparc64-cp0.xml, sparc64-cpu.xml, sparc64-fpu.xml: New files
> for sparc 64-bit.
> * sparc-solaris.xml, sparc64-solaris.xml, sparc-solaris.c,
> sparc64-solaris.c: New files for sparc and sparc64 on Solaris.
* sparc-solaris.c, sparc64-solaris.c: Generated.
> diff -Npur a/gdb/features/sparc-cp0.xml b/gdb/features/sparc-cp0.xml
> --- a/gdb/features/sparc-cp0.xml 1969-12-31 16:00:00.000000000 +0000
> +++ b/gdb/features/sparc-cp0.xml 2016-12-06 03:07:35.249368327 +0000
> @@ -0,0 +1,19 @@
> +<?xml version="1.0"?>
> +<!-- Copyright (C) 2013-2016 Free Software Foundation, Inc.
> +
> + 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. -->
> +
> +<!DOCTYPE feature SYSTEM "gdb-target.dtd">
> +<feature name="org.gnu.gdb.sparc.cp0">
> + <reg name="y" bitsize="32" type="uint32" regnum="64"/>
> + <reg name="psr" bitsize="32" type="uint32" regnum="65"/>
> + <reg name="wim" bitsize="32" type="uint32" regnum="66"/>
> + <reg name="tbr" bitsize="32" type="uint32" regnum="67"/>
> + <reg name="pc" bitsize="32" type="uint32" regnum="68"/>
> + <reg name="npc" bitsize="32" type="uint32" regnum="69"/>
I suspect the type should be code_ptr.
> + <reg name="fsr" bitsize="32" type="uint32" regnum="70"/>
> + <reg name="csr" bitsize="32" type="uint32" regnum="71"/>
> +</feature>
> +
--
Yao (é½å°§)
next prev parent reply other threads:[~2016-12-06 15:26 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 [this message]
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
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=20161206152616.GC28789@E107787-LIN \
--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