Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [11/18] Cell multi-arch: Target description <compatible> infrastructure
Date: Tue, 09 Sep 2008 10:47:00 -0000	[thread overview]
Message-ID: <200809091046.m89AkLpG028281@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <ur67ucug2.fsf@gnu.org> from "Eli Zaretskii" at Sep 08, 2008 10:24:13 PM

Eli Zaretskii wrote:

> Then I suggest to rephrase:
> 
>  +@var{arch} is one of the architectures from the set accepted by
>  +@code{set architecture} (@pxref{Targets, ,Specifying a Debugging
>  +Target}).
> 
> > The wording I've used is copied above is copied from the description
> > of the <architecture> element
> 
> Please fix that one as well.
> 
> > See below for an updated patch.
> 
> Thanks, this is fine (with the above wording change).

Thanks!  For reference, here's the current version of the gdb.texinfo
changes.

Bye,
Ulrich


Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo
+++ src/gdb/doc/gdb.texinfo
@@ -27586,6 +27586,7 @@ are explained further below.
 <!DOCTYPE target SYSTEM "gdb-target.dtd">
 <target version="1.0">
   @r{[}@var{architecture}@r{]}
+  @r{[}@var{compatible}@dots{}@r{]}
   @r{[}@var{feature}@dots{}@r{]}
 </target>
 @end smallexample
@@ -27637,9 +27638,33 @@ An @samp{<architecture>} element has thi
   <architecture>@var{arch}</architecture>
 @end smallexample
 
-@var{arch} is an architecture name from the same selection
-accepted by @code{set architecture} (@pxref{Targets, ,Specifying a
-Debugging Target}).
+@var{arch} is one of the architectures from the set accepted by
+@code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}).
+
+@subsection Compatible Architecture
+@cindex <compatible>
+
+A @samp{<compatible>} element has this form:
+
+@smallexample
+  <compatible>@var{arch}</compatible>
+@end smallexample
+
+@var{arch} is one of the architectures from the set accepted by
+@code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}).
+
+A @samp{<compatible>} element is used to specify that the target
+is able to run binaries in some other than the main target architecture
+given by the @samp{<architecture>} element.  For example, on the
+Cell Broadband Engine, the main architecture is @code{powerpc:common}
+or @code{powerpc:common64}, but the system is able to run binaries
+in the @code{spu} architecture as well.  The way to describe this
+capability with @samp{<compatible>} is as follows:
+
+@smallexample
+  <architecture>@code{powerpc:common}</architecture>
+  <compatible>@code{spu}</compatible>
+@end smallexample
 
 @subsection Features
 @cindex <feature>


-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


      reply	other threads:[~2008-09-09 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07 21:15 Ulrich Weigand
2008-09-08  3:09 ` Eli Zaretskii
2008-09-08 11:45   ` Ulrich Weigand
2008-09-08 19:25     ` Eli Zaretskii
2008-09-09 10:47       ` Ulrich Weigand [this message]

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=200809091046.m89AkLpG028281@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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