From: Rahul Chaturvedi <justanotheraliasforrahul@yahoo.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Questions on the stack for IA64
Date: Wed, 14 Apr 2004 05:34:32 +0000 [thread overview]
Message-ID: <20040414053432.2971.qmail@web61206.mail.yahoo.com> (raw)
In-Reply-To: <20040413051722.84368.qmail@web61202.mail.yahoo.com>
> Rahul> Does the compiler ever touch this backing
> store?
>
> Not directly.
Another question on this, who allocates the memory for
the backing store? What if the RSE runs out of memory
there?
>
> Rahul> I believe it is used during a stack unwind?
>
> Yes (as is the memory stack and the registers).
>
> Rahul> printf("", a, b, c, d, e, f, g, h,
> i, j, k, l, m, n,
> Rahul> o, p, q, r, s, t, u, v, w, x, y, z, aa, bb,
> cc, dd, ee, ff,
> Rahul> gg);
>
> Rahul> As you can see, almost all the parameters
> are being "st4'd"
> Rahul> to memory. From the architecture
> specification, shouldn't all
> Rahul> these be moved into registers? I have a
> total of much lesser
> Rahul> than 96 parameters?
>
> You need to look at the software conventions &
> runtime architecture guide:
>
>
>
http://www.intel.com/design/itanium/downloads/245358.htm
>
> It specifies that up to 8 registers are used for
> argument passing.
>
Oh okay. I'll read the rest of the guide before I ask
more stupid questions on this :)
> There are also some fine books that might help you
> get started. ;-)
Books are expensive (especially in India) :( Processor
manuals and mailing lists are free :)
__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html
next prev parent reply other threads:[~2004-04-14 5:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 5:17 Questions on the stack for IA64 Rahul Chaturvedi
2004-04-13 16:25 ` Luck, Tony
2004-04-13 17:24 ` Chen, Kenneth W
2004-04-14 5:05 ` Rahul Chaturvedi
2004-04-14 5:19 ` David Mosberger
2004-04-14 5:29 ` Ian Wienand
2004-04-14 5:34 ` Rahul Chaturvedi [this message]
2004-04-14 16:06 ` Luck, Tony
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=20040414053432.2971.qmail@web61206.mail.yahoo.com \
--to=justanotheraliasforrahul@yahoo.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