From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [patch] gdbserver support for e500 / altivec
Date: Mon, 15 Oct 2007 20:22:00 -0000 [thread overview]
Message-ID: <20071015200058.GA12978@caradoc.them.org> (raw)
In-Reply-To: <20071005180207.GA4545@caradoc.them.org>
On Fri, Oct 05, 2007 at 02:02:07PM -0400, Daniel Jacobowitz wrote:
> Oh, I suppose this needs a NEWS entry. I'll handle that after it's
> checked in.
I've checked it in, along with this NEWS entry.
--
Daniel Jacobowitz
CodeSourcery
2007-10-15 Daniel Jacobowitz <dan@codesourcery.com>
* NEWS: Mention gdbserver PowerPC improvements.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.242
diff -u -p -r1.242 NEWS
--- NEWS 15 Oct 2007 19:45:30 -0000 1.242
+++ NEWS 15 Oct 2007 20:00:00 -0000
@@ -12,6 +12,9 @@ and in inlined functions.
* Target descriptions can now describe registers for PowerPC.
+* The GDB remote stub, gdbserver, now supports the AltiVec and SPE
+registers on PowerPC targets.
+
*** Changes in GDB 6.7
* Resolved 101 resource leaks, null pointer dereferences, etc. in gdb,
next prev parent reply other threads:[~2007-10-15 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 18:02 Daniel Jacobowitz
2007-10-15 20:22 ` Daniel Jacobowitz [this message]
2007-10-16 22:22 ` Ulrich Weigand
2007-10-17 1:02 ` Daniel Jacobowitz
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=20071015200058.GA12978@caradoc.them.org \
--to=drow@false.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