From: Frederic Marmond <fmarmond@gmail.com>
To: blurrpp@yahoo.com
Cc: linux-assembly@vger.kernel.org
Subject: Re: Passing parameters to assembler functions in 'C' 64 style.
Date: Thu, 4 Dec 2008 21:55:30 +0100 [thread overview]
Message-ID: <200812042155.30433.fmarmond@gmail.com> (raw)
In-Reply-To: <5360.11799.qm@web50303.mail.re2.yahoo.com>
Hi Luke,
maybe this document may answer your question:
http://www.x86-64.org/documentation/abi.pdf
Have a particular look to section 3.2
Fred
Le Thursday 04 December 2008 à 21:20, £ukasz a écrit :
> Hi.
> I started to write assembler functions for C on 64-bit arch. On 32-bit
> arch. every parameters ware put on stack, now is different, what can be
> easyly seen reading source program. For example if im passing one (int *)
> parameter, adress (&int) is kept in %rdi register, and so one if u are
> passing more parameters. Ofcurse is not dificult to use it if u know but is
> there any key according to which parameters are stored?. I've made some
> "experiments" with different numbers and kind parameters, but the "key"
> must be described somewhere.
>
> Luke
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-assembly"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
DeepSee project, few links:
web: http://www.sand-labs.org/deepsee
blog: http://fmarmond.blogspot.com/search/label/DeepSee
twitt: http://twitter.com/fmarmond
IRC: #deepsee on freenode
--
To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-12-04 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 20:20 Passing parameters to assembler functions in 'C' 64 style £ukasz
2008-12-04 20:54 ` Robert Plantz
2008-12-04 20:55 ` Frederic Marmond [this message]
2008-12-04 21:22 ` £ukasz
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=200812042155.30433.fmarmond@gmail.com \
--to=fmarmond@gmail.com \
--cc=blurrpp@yahoo.com \
--cc=linux-assembly@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.