From: Jim Blandy <jimb@codesourcery.com>
To: "Mark Kettenis" <mark.kettenis@xs4all.nl>
Cc: "Ulrich Weigand" <uweigand@de.ibm.com>,
"Daniel Jacobowitz" <drow@false.org>,
gdb-patches@sourceware.org
Subject: Re: [RFA][3/5] New port: Cell BE SPU (the port itself)
Date: Mon, 13 Nov 2006 19:50:00 -0000 [thread overview]
Message-ID: <m3psbrqg5x.fsf@codesourcery.com> (raw)
In-Reply-To: <22583.192.87.1.22.1163421727.squirrel@webmail.xs4all.nl> (Mark Kettenis's message of "Mon, 13 Nov 2006 13:42:07 +0100 (CET)")
"Mark Kettenis" <mark.kettenis@xs4all.nl> writes:
>> I have a set of patches that does appear to work so far; it is based
>> primarily on switching current_gdbarch on thread switch. However,
>> there's still some work to be done before this is in a shape suitable
>> for mainline inclusion.
>
> Andrew Cagney has talked a fair bit about this sort of things in the past.
> His idea was that each frame would have a gdbarch. But a gdbarch per
> thread probably makes more sense.
Not to distract from discussion of Uli's patch, but:
I've worked on a processor that would switch between a normal ISA and
a special VLIW ISA on function calls. The bottom bit of the return
address said which mode to return to on the way out. And ARM allows
calls between Thumb and ARM code.
Making the architecture per-frame, though, raises a bunch of odd
questions. If a register is callee-saves, finding its value in some
frame F entails asking F's callee G for the value. But if G is a
different gdbarch from F, then what register numbering does F use to
make the request?
And that's just off the top of my head. I'll bet there's lots more.
next prev parent reply other threads:[~2006-11-13 19:50 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
2006-11-13 19:50 ` Jim Blandy [this message]
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=m3psbrqg5x.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=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