Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
	 schwab@suse.de,  gdb-patches@sources.redhat.com
Subject: Re: ColdFire/fido support
Date: Wed, 20 Jun 2007 09:14:00 -0000	[thread overview]
Message-ID: <200706201314.06858.vladimir@codesourcery.com> (raw)
In-Reply-To: <E1I0i0L-0000nO-4k@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 411 bytes --]

On Tuesday 19 June 2007 22:00, Eli Zaretskii wrote:
> > Date: Tue, 19 Jun 2007 13:10:30 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Vladimir Prus <vladimir@codesourcery.com>, schwab@suse.de,
> > 	gdb-patches@sources.redhat.com
> > 
> > Maybe that sentence should be inside the
> > description of the three @item / @itemx / @itemx core features?
> 
> Fine with me.

Is the attached OK?

- Volodya

[-- Attachment #2: doc.diff --]
[-- Type: text/x-diff, Size: 1344 bytes --]

--- gdb.texinfo	(revision 4281)
+++ gdb.texinfo	(local)
@@ -25736,6 +25736,13 @@ The names of registers are not case sens
 of recognizing standard features, but @value{GDBN} will only display
 registers using the capitalization used in the description.
 
+@menu
+* ARM Features::
+* M68K Features::
+@end menu
+
+
+@node ARM Features
 @subsection ARM Features
 @cindex target descriptions, ARM features
 
@@ -25751,6 +25758,26 @@ it should contain at least registers @sa
 @samp{wCGR0} through @samp{wCGR3}.  The @samp{wCID}, @samp{wCon},
 @samp{wCSSF}, and @samp{wCASF} registers are optional.
 
+@node M68K Features
+@subsection M68K Features
+@cindex target descriptions, M68K features
+
+@table @code
+@item @samp{org.gnu.gdb.m68k.core}
+@itemx @samp{org.gnu.gdb.coldfire.core}
+@itemx @samp{org.gnu.gdb.fido.core}
+One of those features must be always present. 
+The feature that is present determines which flavor of m86k is
+used.  The feature that is present should contain registers
+@samp{d0} through @samp{d7}, @samp{a0} through @samp{a5}, @samp{fp},
+@samp{sp}, @samp{ps} and @samp{pc}.
+
+@item @samp{org.gnu.gdb.coldfire.fp}
+This feature is optional.  If present, it should contain registers
+@samp{fp0} through @samp{fp7}, @samp{fpcontrol}, @samp{fpstatus} and
+@samp{fpiaddr}.
+@end table
+
 @include gpl.texi
 
 @raisesections

  reply	other threads:[~2007-06-20  9:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05  9:37 Vladimir Prus
2007-05-05 11:02 ` Andreas Schwab
2007-05-06 11:52   ` Vladimir Prus
2007-05-28 11:43     ` Vladimir Prus
2007-06-05 15:19       ` Daniel Jacobowitz
2007-06-08 10:58         ` Vladimir Prus
2007-06-12 13:38           ` Daniel Jacobowitz
2007-06-15 10:17             ` Vladimir Prus
2007-06-15 14:47               ` Daniel Jacobowitz
2007-06-15 19:05                 ` Vladimir Prus
2007-06-16 10:21                   ` Eli Zaretskii
2007-06-19 16:39                     ` Vladimir Prus
2007-06-19 16:53                       ` Eli Zaretskii
2007-06-19 17:10                         ` Daniel Jacobowitz
2007-06-19 18:00                           ` Eli Zaretskii
2007-06-20  9:14                             ` Vladimir Prus [this message]
2007-06-20 18:15                               ` Eli Zaretskii
2007-06-30 15:47       ` Andreas Schwab
2007-06-30 16:00         ` Daniel Jacobowitz

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=200706201314.06858.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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