From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: SPU port for GDB 6.6?
Date: Thu, 23 Nov 2006 14:04:00 -0000 [thread overview]
Message-ID: <200611231404.kANE4HAl010976@d12av02.megacenter.de.ibm.com> (raw)
Joel,
I was wondering whether there was any chance to get the new SPU port
into the GDB 6.6 release as well.
It's mostly target-specific code, but does require some minor
changes to common code. We would be talking about the following
set of patches (already committed to mainline):
http://sources.redhat.com/ml/gdb-patches/2006-11/msg00231.html
http://sources.redhat.com/ml/gdb-patches/2006-11/msg00251.html
http://sources.redhat.com/ml/gdb-patches/2006-11/msg00256.html
http://sources.redhat.com/ml/gdb-patches/2006-11/msg00134.html
Would it be OK to apply those to the 6.6 branch at this stage?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next reply other threads:[~2006-11-23 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 14:04 Ulrich Weigand [this message]
2006-11-24 19:25 ` Joel Brobecker
2006-11-24 20:24 ` Daniel Jacobowitz
2006-11-24 20:29 ` 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=200611231404.kANE4HAl010976@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--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