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: Tue, 26 Jul 2011 18:18:00 -0000 [thread overview]
Message-ID: <201107261844.13460.pedro@codesourcery.com> (raw)
In-Reply-To: <4E2D18F3.6080006@codesourcery.com>
Thanks. This code in this version looked good to me,
with a few nits pointed out below that I noticed this time
around.
The new docs bits will need to be reviewed by Eli. I
have one comment to them:
> @@ -36854,6 +36854,7 @@ registers using the capitalization used in the description.
> * MIPS Features::
> * M68K Features::
> * PowerPC Features::
> +* C6x Features::
> @end menu
The list looked alpha sorted to me.
> +static int tic6x_regmap_c64x[] = {
> + /* A0 - A15 */
> + 51, 50, 53, 52, 55, 54, 57, 56,
> + 59, 58, 61, 60, 63, 62, 65, 64,
> + /* B0 - B15 */
> + 21, 20, 23, 22, 25, 24, 27, 26,
> + 29, 28, 31, 30, 33, 32, 67, 66,
> + /* CSR PC */
> + 3, 2,
> + /* A16 - A31 */
> + 35, 34, 37, 36, 39, 38, 41, 40,
> + 43, 42, 45, 44, 47, 46, 49, 48,
> + /* B16 - B32 */
B31, I think?
> + 5, 4, 7, 6, 9, 8, 11, 10,
> + 13, 12, 15, 14, 17, 16, 19, 18,
> + -1, -1, -1
> + /* CSR PC*/
Missing space. (several places)
> + *base = (void *) ((char *)*base - idx);
Missing space after (char *)
> +#ifdef HAVE_PTRACE_GETREGS
> +
I wonder if there ever was a c6x kernel that
didn't have this.
--
Pedro Alves
next prev parent reply other threads:[~2011-07-26 17:44 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
2011-07-25 7:27 ` Yao Qi
2011-07-26 18:18 ` Pedro Alves [this message]
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=201107261844.13460.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