From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Unwind bug on out of line code called from leaf functions
Date: Thu, 27 Nov 2003 01:34:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106989692626609@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106989195923088@msgid-missing>
>>>>> On Thu, 27 Nov 2003 12:12:56 +1100, Keith Owens <kaos@sgi.com> said:
Keith> On Wed, 26 Nov 2003 16:32:00 -0800,
Keith> David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>>> On Thu, 27 Nov 2003 11:12:18 +1100, Keith Owens <kaos@sgi.com> said:
Keith> We need a generic fix for unwinding through out of line code
Keith> called from leaf functions and not using br.call. The
Keith> obvious solution is to flag all out of line code with an
Keith> unwind abi field and have the common unwind code reset
Keith> ar.pfs. Can I use .unwabi 3, 'o' for out of line?
>> The .unwabi directive isn't appropriate for that. If you want such a
>> feature, please push it through the ABI committee to get it officially
>> supported. I've said that before, I think.
Keith> I disagree, unwabi is exactly what we need for this. The out
Keith> of line code is peculiar to Linux, and uses the Linux pt_regs
Keith> to get the real ar.pfs. .unwabi 3,i indicates a Linux
Keith> interrupt frame with all state in pt_regs, .unwabi 3,o
Keith> indicates a Linux out of line frame with pt_regs.ar_pfs
Keith> containing the real ar.pfs. If unwabi 3,i is valid then so
Keith> is unwabi 3,o.
If you want to support out-of-line code, do it right or don't it at
all. There is no chance in hell I'm going to accept such hacks and I
also won't bother supporting such gross hacks in libunwind. EOD.
--david
next prev parent reply other threads:[~2003-11-27 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 0:12 Unwind bug on out of line code called from leaf functions Keith Owens
2003-11-27 0:32 ` David Mosberger
2003-11-27 1:12 ` Keith Owens
2003-11-27 1:34 ` David Mosberger [this message]
2003-11-27 4:28 ` David Mosberger
2003-11-27 6:52 ` Jim Wilson
2003-12-11 1:21 ` David Mosberger
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=marc-linux-ia64-106989692626609@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.