From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org, drow@false.org
Subject: Re: [rfc/rfa] [3/4] SPU enhancements: gdbserver support
Date: Mon, 04 Jun 2007 13:58:00 -0000 [thread overview]
Message-ID: <200706041358.l54Dw7sd029535@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <E1HutBM-0007Wx-1X@fencepost.gnu.org> from "Eli Zaretskii" at Jun 03, 2007 12:43:56 PM
Eli Zaretskii wrote:
> > > What do you mean by ``keyword''? Isn't @var{object} a _name_ of an
> > > object or its symbol?
> >
> > This is just copied from the pre-existing text (also present in the
> > qXfer::read section). In any case, I think "keyword" is right here,
> > as you can only use one of the defined strings ("auxv", "memory-map",
> > "spu", ...) as "object".
>
> Then please say something like this:
>
> (@var{object} can be @samp{auxv}, @samp{memory-map}, @samp{spu}...)
I guess I may be misunderstanding something, but already today the
paragraph immediately following the quoted sentence says:
"Here are the specific requests of this form defined so far."
and then goes on to describe in detail the auxv, memory-map, etc.
variants.
What would be the benefit of repeating that list once again?
Bye,
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:[~2007-06-04 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 19:33 Ulrich Weigand
2007-06-02 20:33 ` Eli Zaretskii
2007-06-03 13:28 ` Ulrich Weigand
2007-06-03 16:44 ` Eli Zaretskii
2007-06-04 13:58 ` Ulrich Weigand [this message]
2007-06-04 19:19 ` Eli Zaretskii
2007-06-04 20:02 ` Ulrich Weigand
2007-06-04 19:54 ` Daniel Jacobowitz
2007-06-04 20:05 ` Ulrich Weigand
2007-06-04 20:10 ` Daniel Jacobowitz
2007-06-05 18:34 ` Daniel Jacobowitz
2007-06-05 23:02 ` Ulrich Weigand
2007-06-06 17:51 ` Eli Zaretskii
2007-06-12 13:58 ` Daniel Jacobowitz
2007-06-12 14:43 ` 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=200706041358.l54Dw7sd029535@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--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