From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Cc: eliz@gnu.org
Subject: [rfc/rfa] [4/4] SPU enhancements: GDB/MI extensions
Date: Sat, 02 Jun 2007 19:34:00 -0000 [thread overview]
Message-ID: <200706021934.l52JY1ZD005660@d12av02.megacenter.de.ibm.com> (raw)
Hello,
this patch makes the new "info spu" commands available via the GDB/MI
protocol. The Cell Broadband Engine IDE is already able to make use
of these commands and display the SPU status information.
It looks like these are the first platform-specific MI commands, so
I'd appreciate opinions on this ...
Eli, doc changes OK?
Bye,
Ulrich
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.
diff -urNp gdb-orig/gdb/doc/gdb.texinfo gdb-head/gdb/doc/gdb.texinfo
--- gdb-orig/gdb/doc/gdb.texinfo 2007-05-31 18:54:31.000000000 +0200
+++ gdb-head/gdb/doc/gdb.texinfo 2007-06-02 20:02:13.954945166 +0200
@@ -21155,6 +21155,86 @@ fullname="/home/nickrob/myprog.c",line="
(gdb)
@end smallexample
+@subheading The @code{-spu-info-event} Command
+@findex -spu-info-event
+
+@subheading Synopsis
+
+@smallexample
+-spu-info-event
+@end smallexample
+
+Display SPU event facility status. This command is available only
+when @value{GDBN} is debugging the Cell Broadband Engine SPU architecture.
+
+@subheading @value{GDBN} Command
+
+The corresponding @value{GDBN} command is @samp{info spu event}.
+
+@subheading The @code{-spu-info-signal} Command
+@findex -spu-info-signal
+
+@subheading Synopsis
+
+@smallexample
+-spu-info-signal
+@end smallexample
+
+Display SPU signal notification facility status. This command is available
+only when @value{GDBN} is debugging the Cell Broadband Engine SPU architecture.
+
+@subheading @value{GDBN} Command
+
+The corresponding @value{GDBN} command is @samp{info spu signal}.
+
+@subheading The @code{-spu-info-mailbox} Command
+@findex -spu-info-mailbox
+
+@subheading Synopsis
+
+@smallexample
+-spu-info-mailbox
+@end smallexample
+
+Display SPU mailbox facility status. This command is available only when
+@value{GDBN} is debugging the Cell Broadband Engine SPU architecture.
+
+@subheading @value{GDBN} Command
+
+The corresponding @value{GDBN} command is @samp{info spu mailbox}.
+
+@subheading The @code{-spu-info-dma} Command
+@findex -spu-info-dma
+
+@subheading Synopsis
+
+@smallexample
+-spu-info-dma
+@end smallexample
+
+Display MFC DMA status. This command is available only when @value{GDBN}
+is debugging the Cell Broadband Engine SPU architecture.
+
+@subheading @value{GDBN} Command
+
+The corresponding @value{GDBN} command is @samp{info spu dma}.
+
+@subheading The @code{-spu-info-proxydma} Command
+@findex -spu-info-proxydma
+
+@subheading Synopsis
+
+@smallexample
+-spu-info-proxydma
+@end smallexample
+
+Display MFC Proxy-DMA status. This command is available only when
+@value{GDBN} is debugging the Cell Broadband Engine SPU architecture.
+
+@subheading @value{GDBN} Command
+
+The corresponding @value{GDBN} command is @samp{info spu proxydma}.
+
@node Annotations
@chapter @value{GDBN} Annotations
diff -urNp gdb-orig/gdb/mi/mi-cmds.c gdb-head/gdb/mi/mi-cmds.c
--- gdb-orig/gdb/mi/mi-cmds.c 2007-05-09 00:47:48.000000000 +0200
+++ gdb-head/gdb/mi/mi-cmds.c 2007-06-02 20:03:01.093198140 +0200
@@ -100,6 +100,11 @@ struct mi_cmd mi_cmds[] =
{ "signal-handle", { NULL, 0 }, NULL, NULL },
{ "signal-list-handle-actions", { NULL, 0 }, NULL, NULL },
{ "signal-list-signal-types", { NULL, 0 }, NULL, NULL },
+ { "spu-info-event", { "info spu event", 0 }, NULL, NULL },
+ { "spu-info-signal", { "info spu signal", 0 }, NULL, NULL },
+ { "spu-info-mailbox", { "info spu mailbox", 0 }, NULL, NULL },
+ { "spu-info-dma", { "info spu dma", 0 }, NULL, NULL },
+ { "spu-info-proxydma", { "info spu proxydma", 0 }, NULL, NULL },
{ "stack-info-depth", { NULL, 0 }, 0, mi_cmd_stack_info_depth},
{ "stack-info-frame", { NULL, 0 }, 0, mi_cmd_stack_info_frame},
{ "stack-list-arguments", { NULL, 0 }, 0, mi_cmd_stack_list_args},
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next reply other threads:[~2007-06-02 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 19:34 Ulrich Weigand [this message]
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
2007-06-20 0:28 Nick Roberts
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=200706021934.l52JY1ZD005660@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