From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Yao Qi <yao@codesourcery.com>
Subject: Re: [RFA 6/8] New port: TI C6x: gdbserver
Date: Thu, 21 Jul 2011 12:21:00 -0000 [thread overview]
Message-ID: <201107211213.41018.pedro@codesourcery.com> (raw)
In-Reply-To: <4E27D5C7.5090707@codesourcery.com>
On Thursday 21 July 2011 08:31:19, Yao Qi wrote:
> >> +<!DOCTYPE feature SYSTEM "gdb-target.dtd">
> >> +<feature name="org.gnu.gdb.tic6x.cpu">
> >> + <reg name="A0" bitsize="32"/>
> >> + <reg name="A1" bitsize="32"/>
> >> + <reg name="A2" bitsize="32"/>
> >
> > ...
> >
> > These are all general purpose, core registers, right?
> >
>
> Not really. A0-31 and B0-31 are general purpose registers, even there
> are some difference among different C6x cores (such as C62x, C67x, and
> C64x). The rest of them can be regarded as control registers and status
> registers. The target description should be refined for the different
> C6x cores, and I'd like to do it in follow-up patches later. Is it OK?
I'd rather start with things clean than change the target's register
set after the fact, but I won't insist. At least you should document in
the manual which registers the new standard feature org.gnu.gdb.tic6x.cpu
requires (under Standard Target Features) though.
--
Pedro Alves
next prev parent reply other threads:[~2011-07-21 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 2:12 Yao Qi
2011-07-20 18:22 ` Pedro Alves
2011-07-21 9:52 ` Yao Qi
2011-07-21 12:21 ` Pedro Alves [this message]
2011-07-25 7:27 ` Yao Qi
2011-07-26 18:18 ` Pedro Alves
2011-07-27 5:17 ` Yao Qi
2011-07-27 7:01 ` Eli Zaretskii
2011-07-27 8:08 ` Yao Qi
2011-07-27 10:43 ` Eli Zaretskii
2011-07-27 12:32 ` Yao Qi
2011-07-27 14:44 ` Eli Zaretskii
2011-07-27 6:19 ` Yao Qi
2011-07-21 14:04 ` Joseph S. Myers
2011-07-22 10:01 ` Yao Qi
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=201107211213.41018.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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