Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Andreas Schwab <schwab@suse.de>,
	 gdb-patches@sources.redhat.com,  Eli Zaretskii <eliz@gnu.org>
Subject: Re: ColdFire/fido support
Date: Fri, 15 Jun 2007 19:05:00 -0000	[thread overview]
Message-ID: <200706152305.25699.vladimir@codesourcery.com> (raw)
In-Reply-To: <20070615144758.GA10833@caradoc.them.org>

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

On Friday 15 June 2007 18:47, Daniel Jacobowitz wrote:
> On Fri, Jun 15, 2007 at 02:17:24PM +0400, Vladimir Prus wrote:
> > On Tuesday 12 June 2007 17:38, Daniel Jacobowitz wrote:
> > 
> > > > I suppose I can add file-based detection for fido, just like it's done for coldfire,
> > > > but I don't think removing XML-based detection is right. What do you think?
> > > 
> > > Right, sorry - I know what I meant to say, but I didn't say it.
> > > 
> > > Float return behavior is not a property of the target at all; it's a
> > > property of the compiler options used.  decr_pc_after_break is a
> > > target property, though, so we should trust the target.  This isn't
> > > important, though, so feel free to commit without changing this.  If
> > > it causes any problems we can clean it up later.
> > 
> > Ok, excellent.
> > 
> > I attach a patch that differs only by non-taking of address of builtin_types. OK?
> 
> I also wrote:
> 
> > This is mostly OK.  Please add a Makefile.in update for the new
> > #include.  Also, we've added XML support for another target.  So it
> > needs a new section in the manual describing which targets support
> > XML registers, and which registers are required.
> 
> It does still need those.  Other than that it's OK.

Does this doco patch look good?

- Volodya

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

--- gdb.texinfo	(revision 4281)
+++ gdb.texinfo	(local)
@@ -25751,6 +25751,22 @@ 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.
 
+@subsection M68K Features
+@cindex target descriptions, M68K features
+
+An M68K target is required to have either the
+@samp{org.gnu.gdb.m68k.core} feature or the
+@samp{org.gnu.gdb.coldfire.core} feature or the 
+@samp{org.gnu.gdb.fido.core} feature.  Which feature is present
+determines which flavour of m68k is used.  The present feature 
+should contain registers @samp{d0} through @samp{d7}, 
+@samp{a0} through @samp{a5}, @samp{fp}, @samp{sp}, @samp{ps} and 
+@samp{pc}.
+
+The @samp{org.gnu.gdb.coldfire.fp} feature is optional.  If present, it
+should contain registers @samp{fp0} through @samp{fp7},
+@samp{fpcontrol}, @samp{fpstatus} and @samp{fpiaddr}.
+
 @include gpl.texi
 
 @raisesections

  reply	other threads:[~2007-06-15 19:05 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 [this message]
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
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=200706152305.25699.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