public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Questions on the stack for IA64
Date: Wed, 14 Apr 2004 05:19:47 +0000	[thread overview]
Message-ID: <16508.51699.368241.279836@napali.hpl.hp.com> (raw)
In-Reply-To: <20040413051722.84368.qmail@web61202.mail.yahoo.com>

>>>>> On Tue, 13 Apr 2004 22:05:56 -0700 (PDT), Rahul Chaturvedi <justanotheraliasforrahul@yahoo.com> said:

  Rahul> Does the compiler ever touch this backing store?

Not directly.

  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.

There are also some fine books that might help you get started. ;-)

	--david
--
Interested in learning more about IA-64 Linux?  Try http://www.lia64.org/book/

  parent reply	other threads:[~2004-04-14  5:19 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 [this message]
2004-04-14  5:29 ` Ian Wienand
2004-04-14  5:34 ` Rahul Chaturvedi
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=16508.51699.368241.279836@napali.hpl.hp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox