From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Incorrect unwind data in entry.S
Date: Fri, 05 Jan 2001 18:48:45 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205882@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205870@msgid-missing>
>>>>> On Thu, 21 Dec 2000 14:42:45 +1100, Keith Owens <kaos@ocs.com.au> said:
Keith> The prologue after .ret21 makes no sense. Unwind claims that
Keith> we are increasing the stack by 416 and spilling registers to
Keith> stack but we are really removing the struct switch_stack.
The code is correct. A prologue always describes the _current state_
of the frame, not the _changes_ to the frame (which would make no
sense). In other words, the code says that after the
load_switch_stack, the frame is back to the original state (switch
stack is gone).
--david
next prev parent reply other threads:[~2001-01-05 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 3:42 [Linux-ia64] Incorrect unwind data in entry.S Keith Owens
2001-01-05 18:48 ` David Mosberger [this message]
2001-01-06 0:51 ` Keith Owens
2001-01-06 1:58 ` David Mosberger
2001-01-16 23:41 ` Cary Coutant
2001-01-17 1:34 ` David Mosberger
2001-01-17 18:54 ` Cary Coutant
2001-01-17 20:04 ` 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-105590678205882@msgid-missing \
--to=davidm@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.