public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Rahul Chaturvedi <justanotheraliasforrahul@yahoo.com>
To: linux-ia64@vger.kernel.org
Subject: Questions on the stack for IA64
Date: Tue, 13 Apr 2004 05:17:22 +0000	[thread overview]
Message-ID: <20040413051722.84368.qmail@web61202.mail.yahoo.com> (raw)

(***I would appreciate it if you'd cc your reply to
this mail address since I am not a member of this
list***)

I have been trying to figure out exactly how the stack
mechanisms available on IA-64 work internally for a
while now. I've made a few observations which I had a
few questions on,

a.) The stack pointer seems to be r12, which is
pointing to a location along the lines of,

0x60000fffffffxxxx

Shouldn't this address be in the 0x8xxxxxxxxxxxxxxx
range? Isn't the 0x6xxxxxxxxxxxxxxx range reserved for
the data segment?

I also checked the address of a global variable, and
it was stored at in the 0x6xxxxxxxxxxxxxxx range.
Wouldn't the stack and the data segment conflict?

b.) There is something called $GP and $TP that the
compiler defines as r1 and r13 respectively. Anyone
got any idea what they are?

c.) How exactly is the data stored in the bspstore
locations?

d.) The pfs register seems to point to a location in
0xcxxxxxxxxxxxxxxx. Shouldn't this point to some
accessible memory location (from usermode)?

e.) For some reason, compiled code, even with full
optimizations seems to do a "st8" on any value I put
in a local variable. For example, I have a function
with about 40 variables, the intel compiler that I am
using does something like,

mov r47, value
st8 [r48], r47

GCC also does something similar.

Shouldn't the compiler simply store the value in r47
instead of st8'ing it to memory when using full
optimizations (-O2)?


Please forgive me if my questions seem a bit naive, my
experience with IA64 is very limited.


I'd also like to remind you to please CC this address
on your reply :)


Thanks


	
		
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/

             reply	other threads:[~2004-04-13  5:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  5:17 Rahul Chaturvedi [this message]
2004-04-13 16:25 ` Questions on the stack for IA64 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
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=20040413051722.84368.qmail@web61202.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