From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Why large stack frame for PAL call
Date: Sun, 27 Jun 2004 17:42:14 +0000 [thread overview]
Message-ID: <200406271740.i5RHeaY24803@unix-os.sc.intel.com> (raw)
Does anyone know why we need such large stack frame for PAL static
call? PAL isn't even suppose to touch any stack register for static
calling convention. Is it for legacy reason or something?
GLOBAL_ENTRY(ia64_pal_call_static)
.prologue ASM_UNW_PRLG_RP|ASM_UNW_PRLG_PFS, ASM_UNW_PRLG_GRSAVE(6)
alloc loc1 = ar.pfs,6,90,0,0
GLOBAL_ENTRY(ia64_pal_call_phys_static)
.prologue ASM_UNW_PRLG_RP|ASM_UNW_PRLG_PFS, ASM_UNW_PRLG_GRSAVE(6)
alloc loc1 = ar.pfs,6,90,0,0
96 local registers?
Also caller is support to setup callee's stack frame for PAL stacked
convention? Wasn't clear from the PAL spec. Though I couldn't make
up any story why it needs to.
next reply other threads:[~2004-06-27 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 17:42 Chen, Kenneth W [this message]
2004-06-29 5:50 ` Why large stack frame for PAL call David Mosberger
2004-06-29 14:11 ` n0ano
2004-06-29 15:13 ` Chen, Kenneth W
2004-06-29 16:20 ` Mallick, Asit K
2004-06-29 21:43 ` 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=200406271740.i5RHeaY24803@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox