Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org, eliz@gnu.org
Subject: [rfa] Mention new spu features in NEWS
Date: Thu, 14 Jun 2007 19:58:00 -0000	[thread overview]
Message-ID: <200706141958.l5EJweUO015972@d12av02.megacenter.de.ibm.com> (raw)

Hello Eli,

I promised to mention the new spu features in NEWS.
Is the following text OK?

Bye,
Ulrich


ChangeLog:

	* NEWS: Mention "info spu" commands and qXfer:spu:read and
	qXfer:spu:write remote packet types.

diff -urNp gdb-orig/gdb/NEWS gdb-head/gdb/NEWS
--- gdb-orig/gdb/NEWS	2007-06-14 14:53:59.000000000 +0200
+++ gdb-head/gdb/NEWS	2007-06-14 21:54:15.508640749 +0200
@@ -74,6 +74,11 @@ show sysroot
   general version of "set solib-absolute-prefix", which is now
   an alias to "set sysroot".
 
+info spu
+  Provide extended SPU facility status information.  This set of
+  commands is available only when debugging the Cell/B.E. SPU
+  architecture.
+
 * New native configurations
 
 OpenBSD/sh			sh*-*openbsd*
@@ -100,6 +105,11 @@ qXfer:features:read:
   Read an XML target description from the target, which describes its
   features.
 
+qXfer:spu:read:
+qXfer:spu:write:
+  Read or write contents of an spufs file on the target system.  These
+  packets are available only on the Cell/B.E. SPU architecture.
+
 * Removed targets
 
 Support for these obsolete configurations has been removed.
-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


             reply	other threads:[~2007-06-14 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 19:58 Ulrich Weigand [this message]
2007-06-15  7:19 ` Eli Zaretskii
2007-06-15 12:42   ` 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=200706141958.l5EJweUO015972@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