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: Mon, 08 Sep 2008 11:45:00 -0000 [thread overview]
Message-ID: <200809081145.m88Bj171030625@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <uzlmjcp22.fsf@gnu.org> from "Eli Zaretskii" at Sep 08, 2008 06:08:21 AM
Eli Zaretskii wrote:
> > +@var{arch} is an architecture name from the same selection
> > +accepted by @code{set architecture} (@pxref{Targets, ,Specifying a
> > +Debugging Target}).
>
> I don't understand the purpose of "the same" here. Same as what?
This element accepts the same set of architecture names as the set
accepted by the "set architecture" command.
The wording I've used is copied above is copied from the description
of the <architecture> element (which also accepts the same set of
architecture names). If you can suggest a clearer way to express
this, I think both places should be fixed ...
> This begs a continuation:
>
> The way to describe this capability with @samp{<compatible>} is as
> follows:
>
> @smallexample
> ...
> @end smallexample
Added. See below for an updated patch.
Thanks,
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
@@ -27641,6 +27642,32 @@ An @samp{<architecture>} element has thi
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 an architecture name from the same selection
+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
next prev parent reply other threads:[~2008-09-08 11:45 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 [this message]
2008-09-08 19:25 ` Eli Zaretskii
2008-09-09 10:47 ` Ulrich Weigand
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=200809081145.m88Bj171030625@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