9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug in asm.ps
Date: Mon,  6 Mar 2006 10:36:10 -0500	[thread overview]
Message-ID: <d26ca0cb0eb5957e13fb6d94468d4e23@coraid.com> (raw)
In-Reply-To: <599f06db0603060731w45549c3bw64296d1f17379498@mail.gmail.com>

Oh, I understand now.  You are correct.  Asm.ps is wrong.

> Ok, but what I meant is that the automatics are upside down growing from n
> to 0 as the memory grows. Of course if you call any functions, the SP points
> to the last space left for their arguments. As far as I understand if you dont
> call any functions, 0(SP) is the last automatic. If you dont have any
> automatics, SP points to the return PC. If you call any functions there is space
> for their args (probably for the args of the functions with the
> biggest number of args) and SP is pointing to the last space which
> will be the first arg, because
> they gro from 0 to n as the memory grows.
>
> On 3/6/06, Brantley Coile <brantley@coraid.com> wrote:
>> SP doesn't point to the last automatic on the stack.
>> Not only is the automatics on the local stack, but also
>> temporaries, like the ones to hold parameters to a function.
>> If you call any functions 4(SP) is the second parameter to functions.
>>
>>



  reply	other threads:[~2006-03-06 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 15:12 Gorka guardiola
2006-03-06 15:16 ` Brantley Coile
2006-03-06 15:31   ` Gorka guardiola
2006-03-06 15:36     ` Brantley Coile [this message]
2006-03-06 15:53       ` Russ Cox
2006-03-06 16:05         ` Brantley Coile
2006-03-06 16:17           ` Russ Cox
2006-03-06 16:22             ` Brantley Coile
2006-03-06 16:28               ` Russ Cox
2006-03-06 16:33                 ` Gorka guardiola
2006-03-06 16:56                   ` Charles Forsyth
2006-03-06 16:16         ` Gorka guardiola

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=d26ca0cb0eb5957e13fb6d94468d4e23@coraid.com \
    --to=brantley@coraid.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).