From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Yao Qi <yao@codesourcery.com>
Subject: Re: [RFA 5/8] New port: TI C6x: gdb port
Date: Thu, 04 Aug 2011 15:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1108041510140.26774@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201108041333.42945.pedro@codesourcery.com>
On Thu, 4 Aug 2011, Pedro Alves wrote:
> Seems like there are a lot of non-core registers here. Now that
> the gdbserver patch has been updated to send in standard tic6x xml
> register description features, all registers the target includes in the
> description that are not part of the defined features should not need
> to be hardcoded in gdb, since the xml description itself will describe
> their sizes and names. See arm-tdep.c:arm_register_name for example.
> More comments on this further down.
Won't GDB need a list of how the register names correspond to DWARF
register numbers (which are allocated for all these registers) somewhere?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-08-04 15:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 2:10 Yao Qi
2011-07-25 11:32 ` Yao Qi
2011-08-03 1:15 ` ping: " Yao Qi
2011-08-04 12:34 ` Pedro Alves
2011-08-04 15:11 ` Joseph S. Myers [this message]
2011-08-04 17:45 ` Pedro Alves
2011-08-04 19:48 ` Joseph S. Myers
2011-08-05 2:13 ` Yao Qi
2011-08-06 2:26 ` Yao Qi
2011-08-08 13:04 ` Pedro Alves
2011-08-09 2:52 ` Yao Qi
2011-08-09 14:01 ` Pedro Alves
2011-08-09 15:16 ` Yao Qi
2011-08-09 15:42 ` Pedro Alves
2011-08-10 2:37 ` Yao Qi
2011-08-10 13:44 ` Pedro Alves
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=Pine.LNX.4.64.1108041510140.26774@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--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