From: Giacomo Tesio <giacomo@tesio.it>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] FP register usage in Plan9 assembler
Date: Tue, 2 Feb 2016 00:34:41 +0100 [thread overview]
Message-ID: <CAHL7psGHc=VLcLh_e3ejGVO8afP1VJs6goRFERWnQYfjWpi+Ew@mail.gmail.com> (raw)
In-Reply-To: <732b1707b783c57f27b9c26d5e9c0900@felloff.net>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Thanks for the explainations!
I did read in the Pike's paper about the syntax name+offset(FP), but I did
understood that name had to be a symbol already defined, and I was looking
for it in the c code. Sorry for the noise!
This led me to another question, however: I've read before that the plan9
compilers use the stack for va_list, but here the assembler is using it
also for explicit parameters, right?
Is it correct to say that this means that the Plan9 compiler suite *never*
follows the sysV calling convention documented at section 3.2.3 of AMD64
ABI http://www.x86-64.org/documentation/abi.pdf and always pushes
parameters to the stack?
Giacomo
2016-02-01 23:48 GMT+01:00 <cinap_lenrek@felloff.net>:
> FP is a translated to a varying offset to SP depending on where in the
> program
> you are. arguments on the stack are padded to 8 bytes on amd64, the first
> argument
> is not passed on the stack on function entry, but passed in BP register
> (RARG is an
> alias for that), however the slot on the stack for first arg is still
> reserved
> so we have a save place to splill it. so 0(FP) is first function argument
> on the
> stack, 8(FP) second argument 16(FP) third ect...
>
> --
> cinap
>
>
[-- Attachment #2: Type: text/html, Size: 1680 bytes --]
next prev parent reply other threads:[~2016-02-01 23:34 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
2016-02-01 22:48 ` cinap_lenrek
2016-02-01 23:34 ` Giacomo Tesio [this message]
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='CAHL7psGHc=VLcLh_e3ejGVO8afP1VJs6goRFERWnQYfjWpi+Ew@mail.gmail.com' \
--to=giacomo@tesio.it \
--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).