From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [RFA][3/5] New port: Cell BE SPU (the port itself)
Date: Mon, 13 Nov 2006 13:48:00 -0000 [thread overview]
Message-ID: <20061113134739.GA20834@nevyn.them.org> (raw)
In-Reply-To: <22583.192.87.1.22.1163421727.squirrel@webmail.xs4all.nl>
On Mon, Nov 13, 2006 at 01:42:07PM +0100, Mark Kettenis wrote:
> That's not really what I'm talking about. I'm talking about having a single
> gdb binary that is able to execute both native powerpc code and spu code
> (but not at the same time). As far as I can tell, it should be possible
> to do that by implementing to_can_run() in both ppc-linux-nat.c and
> spu-linux-nat.c, such that only one returns true at any time.
Hmm, I guess that would work. Would you include this in all native
ppc64 debuggers?
> I don't agree with Daniel here. The spu-linux-nat.c target vector is
> only usable on a powerpc native debugger.
Fair enough. I think of this as similar to a hypothetical remote-*.c
module which is only usable on Windows, but I agree that it's not a
good analogy.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-13 13:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 18:39 Ulrich Weigand
2006-11-11 21:19 ` Mark Kettenis
2006-11-12 15:38 ` Ulrich Weigand
2006-11-12 21:42 ` Mark Kettenis
2006-11-12 22:12 ` Daniel Jacobowitz
2006-11-13 12:27 ` Ulrich Weigand
2006-11-13 12:43 ` Mark Kettenis
2006-11-13 13:48 ` Daniel Jacobowitz [this message]
2006-11-13 19:50 ` Jim Blandy
2006-11-18 0:10 ` Ulrich Weigand
2006-11-18 6:03 ` Daniel Jacobowitz
2006-11-18 11:10 ` Ulrich Weigand
2006-11-18 16:41 ` Daniel Jacobowitz
2006-11-18 17:35 ` Mark Kettenis
2006-11-21 20:22 ` Ulrich Weigand
2006-11-21 20:40 ` Daniel Jacobowitz
2006-11-21 21:32 ` Mark Kettenis
2006-11-22 14:13 ` Ulrich Weigand
2006-11-22 18:43 ` Daniel Jacobowitz
2006-11-22 19:46 ` 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=20061113134739.GA20834@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--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