Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: [rfc/rfa] [4/4] SPU enhancements: GDB/MI extensions
Date: Wed, 20 Jun 2007 00:28:00 -0000	[thread overview]
Message-ID: <18040.29844.135942.62041@kahikatea.snap.net.nz> (raw)


On Sat, 2 Jun 2007 21:34:01 +0200 (CEST) Ulrich Weigand writes:
>...
> ChangeLog:

> 	* mi/mi-cmds.c (mi_cmds): Add -spu-info-event, -spu-info-signal,
> 	-spu-info-mailbox, -spu-info-dma, and -spu-info-proxydma commands.

> doc/ChangeLog:

> 	* gdb.texinfo (GDB/MI Miscellaneous Commands): Document -spu-info
> 	commands.


I don't think the description of these command belongs to the node
GDB/MI Miscellaneous Commands, but a node of it's own within a new node
called something like "GDB/MI Architecture Specific Commands".

Also I agree with Daniel J's remarks about a MI command like -arch-info.  I
don't know if general purpose software like Emacs could run on the Cell
Broadband Engine, but without such a command, presumably the above ones are
enhancements of GDB for the Cell Broadband Engine IDE only.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


             reply	other threads:[~2007-06-20  0:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20  0:28 Nick Roberts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-02 19:34 Ulrich Weigand
2007-06-02 20:38 ` Eli Zaretskii
2007-06-03 13:29   ` Ulrich Weigand
2007-06-03 16:45     ` Eli Zaretskii
2007-06-04 20:00 ` Daniel Jacobowitz
2007-06-04 20:13   ` Ulrich Weigand
2007-06-04 20:22     ` Daniel Jacobowitz
2007-06-04 22:59       ` Ulrich Weigand
2007-06-05 11:12         ` Daniel Jacobowitz
2007-06-14 20:05           ` Ulrich Weigand
2007-06-21  2:23             ` Ricardo Marin Matinata
2007-06-21 22:22               ` Nick Roberts
2007-06-22 20:53               ` Jim Blandy

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=18040.29844.135942.62041@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.com \
    /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