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: Wed, 20 Jul 2011 18:22:00 -0000 [thread overview]
Message-ID: <201107201855.09188.pedro@codesourcery.com> (raw)
In-Reply-To: <4E2638CE.7050205@codesourcery.com>
On Wednesday 20 July 2011 03:09:18, Yao Qi wrote:
> +static CORE_ADDR
> +tic6x_get_pc (struct regcache *regcache)
> +{
> + union tic6x_register pc;
> + collect_register_by_name (regcache, "PC", pc.buf);
Empty line missing after declaration. At least one more instance.
> +int *tic6x_regmap;
> +
...
> +unsigned int tic6x_breakpoint;
Could be static?
> s390-linux32-expedite = r14,r15,pswa
> s390-linux64-expedite = r14l,r15l,pswa
> s390x-linux64-expedite = r14,r15,pswa
> +tic6x-linux-expedite = A15,PC
Stupid question: is there a reason all register
names are all caps in C6x?
> +++ b/gdb/features/tic6x-linux.xml
> @@ -0,0 +1,12 @@
> +<?xml version="1.0"?>
> +<!-- Copyright (C) 2010, 2011 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 target SYSTEM "gdb-target.dtd">
> +<target>
> + <architecture>tic6x</architecture>
Since this is for linux only, add:
<osabi>GNU/Linux</osabi>
> + <xi:include href="tic6x-cpu.xml"/>
> +</target>
> +#elif defined(__TMS320C6X__)
> +#define PT_TEXT_ADDR 0x10000*4
> +#define PT_DATA_ADDR 0x10004*4
> +#define PT_TEXT_END_ADDR 0x10008*4
Surround with parens as principle to avoid precedence
surprises:
#define PT_TEXT_ADDR (0x10000*4)
> +<!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?
Otherwise looks fine to me.
--
Pedro Alves
next prev parent reply other threads:[~2011-07-20 17:55 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 [this message]
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
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=201107201855.09188.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