From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] FP register usage in Plan9 assembler
Date: Mon, 1 Feb 2016 22:44:45 +0000 [thread overview]
Message-ID: <CAOw7k5jTo162LyNpqJyHw6i49zwt4vtETbvgrCLRZ=qfiJRYYg@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5hHmw4U29pHN0+SSCKdYUqR61Fd9s6JRvsemAEu+-VxTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
On 1 February 2016 at 22:38, Charles Forsyth <charles.forsyth@gmail.com>
wrote:
> the syntax name+offset(FP) defines name as the given offset from the
> virtual frame pointer.
I ought to have added that it's +8 because info is the second parameter,
where the parameter space is
divided into slots of 8 bytes on amd64 and 4 bytes on the 32-bit
architectures. on amd64, the first parameter is passed in a register (BP);
as on some of the RISC machines. on amd64, the second parameter is +8(FP),
third is +16(FP), and so on.
on x86/32 the first parameter is passed on the stack, so it's +0(FP),
+4(FP), ...
[-- Attachment #2: Type: text/html, Size: 1036 bytes --]
next prev parent reply other threads:[~2016-02-01 22:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 16:47 Giacomo Tesio
2016-02-01 22:38 ` Charles Forsyth
2016-02-01 22:44 ` Charles Forsyth [this message]
2016-02-01 22:48 ` cinap_lenrek
2016-02-01 23:34 ` Giacomo Tesio
2016-02-02 0:36 ` Charles Forsyth
2016-02-02 0:58 ` Giacomo Tesio
2016-02-02 12:39 ` Aram Hăvărneanu
2016-02-02 16:42 ` Steven Stallion
2016-02-02 17:16 ` lucio
2016-02-03 15:24 ` erik quanstrom
2016-02-03 15:51 ` Steven Stallion
2016-02-03 16:36 ` erik quanstrom
2016-02-04 10:08 ` Aram Hăvărneanu
2016-02-04 12:04 ` lucio
2016-02-04 15:58 ` Ryan Gonzalez
2016-02-04 16:09 ` lucio
2016-02-04 18:06 ` Ryan Gonzalez
2016-02-04 18:14 ` balaji
2016-02-04 18:28 ` Ryan Gonzalez
2016-02-04 19:31 ` Skip Tavakkolian
2016-02-04 12:24 ` Brantley Coile
2016-02-04 12:53 ` lucio
2016-02-04 14:57 ` erik quanstrom
2016-02-04 14:05 ` Aram Hăvărneanu
2016-02-04 14:10 ` Aram Hăvărneanu
2016-02-04 14:30 ` Aram Hăvărneanu
2016-02-04 15:07 ` Charles Forsyth
2016-02-04 15:16 ` erik quanstrom
2016-02-04 15:11 ` erik quanstrom
2016-02-04 15:22 ` erik quanstrom
2016-02-04 15:26 ` Charles Forsyth
2016-02-04 20:34 ` erik quanstrom
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='CAOw7k5jTo162LyNpqJyHw6i49zwt4vtETbvgrCLRZ=qfiJRYYg@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).