From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [RFA 6/8] New port: TI C6x: gdbserver
Date: Wed, 27 Jul 2011 12:32:00 -0000 [thread overview]
Message-ID: <4E2FEBB6.9040106@codesourcery.com> (raw)
In-Reply-To: <E1Qm14l-0007Ad-Cu@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On 07/27/2011 06:10 PM, Eli Zaretskii wrote:
>> > gdb/doc/
>> > * gdb.texinfo (Standard Target Features): Document C6x features.
> Please add
> (TIC6x Features): New node.
>
Added.
>> > +@V@/gdb/features/tic6x-core.xml @V@/gdb/features/tic6x-gp.xml
>> > +@V@/gdb/features/tic6x-c6xp.xml @V@/gdb/features/tic6x-c62x-linux.xml
> These entries cause a file on the left to be renamed to the name on
> the right when the tarball is unpacked. The new names should not
> clash after 8+3 truncation. So the added entries are incorrect.
>
Looks like I misunderstood this file. Fixed in new patch.
--
Yao (é½å°§)
[-- Attachment #2: 0005-target-description.patch --]
[-- Type: text/x-patch, Size: 3935 bytes --]
gdb/doc/
* gdb.texinfo (Standard Target Features): Document C6x features.
(TIC6x Features): New node.
gdb/
* config/djgpp/fnchange.lst: Add features/tic6x-*.xml and
features/tic6x-*.c files.
Add regformats/tic6x-*-linux.dat files.
Add tic6x-tdep.c, tic6x-tdep.h and tic6x-linux-tdep.c.
---
gdb/config/djgpp/fnchange.lst | 15 +++++
gdb/doc/gdb.texinfo | 16 ++++++
diff --git a/gdb/config/djgpp/fnchange.lst b/gdb/config/djgpp/fnchange.lst
index 4b86c31..941abb2 100644
--- a/gdb/config/djgpp/fnchange.lst
+++ b/gdb/config/djgpp/fnchange.lst
@@ -240,6 +240,15 @@
@V@/gdb/features/i386/i386-mmx.c @V@/gdb/features/i386/i32-m.c
@V@/gdb/features/i386/i386-mmx-linux.xml @V@/gdb/features/i386/i32-ml.xml
@V@/gdb/features/i386/i386-mmx.xml @V@/gdb/features/i386/i32-m.xml
+@V@/gdb/features/tic6x-core.xml @V@/gdb/features/c6x-core.xml
+@V@/gdb/features/tic6x-gp.xml @V@/gdb/features/c6x-gp.xml
+@V@/gdb/features/tic6x-c6xp.xml @V@/gdb/features/c6x-c6xp.xml
+@V@/gdb/features/tic6x-c62x-linux.xml @V@/gdb/features/c6x-62xl.xml
+@V@/gdb/features/tic6x-c64x-linux.xml @V@/gdb/features/c6x-64xl.xml
+@V@/gdb/features/tic6x-c64xp-linux.xml @V@/gdb/features/c6x64xpl.xml
+@V@/gdb/features/tic6x-c64xp-linux.c @V@/gdb/features/c6x64xpl.c
+@V@/gdb/features/tic6x-c64x-linux.c @V@/gdb/features/c6x-64xl.c
+@V@/gdb/features/tic6x-c62x-linux.c @V@/gdb/features/c6x-62xl.c
@V@/gdb/f-exp.tab.c @V@/gdb/f-exp_tab.c
@V@/gdb/gdbserver/linux-cris-low.c @V@/gdb/gdbserver/lx-cris.c
@V@/gdb/gdbserver/linux-crisv32-low.c @V@/gdb/gdbserver/lx-cris32.c
@@ -341,6 +350,9 @@
@V@/gdb/regformats/rs6000/powerpc-vsx64l.dat @V@/gdb/regformats/rs6000/ppc-v64l.dat
@V@/gdb/regformats/rs6000/powerpc-cell32l.dat @V@/gdb/regformats/rs6000/ppc-c32l.dat
@V@/gdb/regformats/rs6000/powerpc-cell64l.dat @V@/gdb/regformats/rs6000/ppc-c64l.dat
+@V@/gdb/regformats/tic6x-c62x-linux.dat @V@/gdb/regformats/c6x-62xl.dat
+@V@/gdb/regformats/tic6x-c64x-linux.dat @V@/gdb/regformats/c6x-64xl.dat
+@V@/gdb/regformats/tic6x-c64xp-linux.dat @V@/gdb/regformats/c6x64xpl.dat
@V@/gdb/remote-e7000.c @V@/gdb/rmt-e7000.c
@V@/gdb/remote-est.c @V@/gdb/rmt-est.c
@V@/gdb/remote-mips.c @V@/gdb/rmt-mips.c
@@ -368,6 +380,9 @@
@V@/gdb/sparc-linux-tdep.c @V@/gdb/splx-tdep.c
@V@/gdb/sparc-sol2-nat.c @V@/gdb/spsol2-nat.c
@V@/gdb/sparc-sol2-tdep.c @V@/gdb/spsol2-tdep.c
+@V@/gdb/tic6x-tdep.c @V@/gdb/c6x-tdep.c
+@V@/gdb/tic6x-tdep.h @V@/gdb/c6x-tdep.h
+@V@/gdb/tic6x-linux-tdep.c @V@/gdb/c6xl-tdep.c
@V@/gdb/testsuite/.gdbinit @V@/gdb/testsuite/gdb.ini
@V@/gdb/testsuite/gdb.arch/altivec-abi.c @V@/gdb/testsuite/gdb.arch/av-abi.c
@V@/gdb/testsuite/gdb.arch/altivec-abi.exp @V@/gdb/testsuite/gdb.arch/av-abi.exp
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 37c81b8..b5b6c74 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -36854,6 +36854,7 @@ registers using the capitalization used in the description.
* MIPS Features::
* M68K Features::
* PowerPC Features::
+* TIC6x Features::
@end menu
@@ -37015,6 +37016,21 @@ contain registers @samp{ev0h} through @samp{ev31h}, @samp{acc}, and
these to present registers @samp{ev0} through @samp{ev31} to the
user.
+@node TIC6x Features
+@subsection TMS320C6x Features
+@cindex target descriptions, TIC6x features
+@cindex target descriptions, TMS320C6x features
+The @samp{org.gnu.gdb.tic6x.core} feature is required for TMS320C6x
+targets. It should contain registers @samp{A0} through @samp{A15},
+registers @samp{B0} through @samp{B15}, @samp{CSR} and @samp{PC}.
+
+The @samp{org.gnu.gdb.tic6x.gp} feature is optional. It should
+contain registers @samp{A16} through @samp{A31} and @samp{B16}
+through @samp{B31}.
+
+The @samp{org.gnu.gdb.tic6x.c6xp} feature is optional. It should
+contain registers @samp{TSR}, @samp{ILC} and @samp{RILC}.
+
@node Operating System Information
@appendix Operating System Information
@cindex operating system information
next prev parent reply other threads:[~2011-07-27 10:43 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
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 [this message]
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=4E2FEBB6.9040106@codesourcery.com \
--to=yao@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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