From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Emi SUZUKI <emi-suzuki@tjsys.co.jp>, gdb-patches@sourceware.org
Subject: Re: [rfc] [2/4] SPU overlay support: The SPU target part
Date: Fri, 11 May 2007 19:33:00 -0000 [thread overview]
Message-ID: <20070511193306.GA7017@caradoc.them.org> (raw)
In-Reply-To: <200705111909.l4BJ9SKO022937@d12av02.megacenter.de.ibm.com>
On Fri, May 11, 2007 at 09:09:28PM +0200, Ulrich Weigand wrote:
> The return stub isn't on the stack either. We'd have to manufacture
> an extra zero-sized stack frame between caller and callee, with
> special unwind rules to be able to continue the backtrace. I guess
> this would be possible somehow, but I still don't see that this would
> provide any benefit to most users ...
Oh... I see how it works now.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-05-11 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 22:26 Ulrich Weigand
2007-05-08 8:10 ` Emi SUZUKI
2007-05-08 12:40 ` Ulrich Weigand
2007-05-10 21:55 ` Daniel Jacobowitz
2007-05-10 22:20 ` Ulrich Weigand
2007-05-11 17:32 ` Daniel Jacobowitz
2007-05-11 19:09 ` Ulrich Weigand
2007-05-11 19:33 ` Daniel Jacobowitz [this message]
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=20070511193306.GA7017@caradoc.them.org \
--to=drow@false.org \
--cc=emi-suzuki@tjsys.co.jp \
--cc=gdb-patches@sourceware.org \
--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