From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [1/9] Cell multi-arch: Target description <compatible> infrastructure
Date: Thu, 23 Jul 2009 12:09:00 -0000 [thread overview]
Message-ID: <200907231207.n6NC7uu7010718@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <83vdlk4maz.fsf@gnu.org> from "Eli Zaretskii" at Jul 22, 2009 09:14:44 PM
Eli Zaretskii wrote:
> > Date: Wed, 22 Jul 2009 19:14:46 +0200 (CEST)
> > From: "Ulrich Weigand" <uweigand@de.ibm.com>
> >
> > +@subsection Compatible Architecture
> > +@cindex <compatible>
>
> @code{<compatible>}, please.
>
> > +@smallexample
> > + <architecture>@code{powerpc:common}</architecture>
> > + <compatible>@code{spu}</compatible>
> > +@end smallexample
>
> You don't need @code inside @smallexample, because the latter uses the
> @code typeface by default.
>
> OK with these changes.
Here's the updated version of the gdb.texinfo patch:
Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo
+++ src/gdb/doc/gdb.texinfo
@@ -30807,6 +30807,7 @@ are explained further below.
<target version="1.0">
@r{[}@var{architecture}@r{]}
@r{[}@var{osabi}@r{]}
+ @r{[}@var{compatible}@r{]}
@r{[}@var{feature}@dots{}@r{]}
</target>
@end smallexample
@@ -30858,9 +30859,8 @@ 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 OS ABI
@cindex @code{<osabi>}
@@ -30877,6 +30877,34 @@ An @samp{<osabi>} element has this form:
@var{abi-name} is an OS ABI name from the same selection accepted by
@w{@code{set osabi}} (@pxref{ABI, ,Configuring the Current ABI}).
+@subsection Compatible Architecture
+@cindex @code{<compatible>}
+
+This optional field was introduced in @value{GDBN} version 7.0.
+Previous versions of @value{GDBN} ignore it.
+
+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>powerpc:common</architecture>
+ <compatible>spu</compatible>
+@end smallexample
+
@subsection Features
@cindex <feature>
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2009-07-23 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 17:15 Ulrich Weigand
2009-07-22 18:18 ` Eli Zaretskii
2009-07-23 12:09 ` Ulrich Weigand [this message]
2009-07-23 19:26 ` Eli Zaretskii
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=200907231207.n6NC7uu7010718@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