From: Robert Plantz <plantz@sonoma.edu>
To: blurrpp@yahoo.com
Cc: linux-assembly@vger.kernel.org
Subject: Re: Passing parameters to assembler functions in 'C' 64 style.
Date: Thu, 04 Dec 2008 12:54:18 -0800 [thread overview]
Message-ID: <1228424058.5690.31.camel@bob-desktop> (raw)
In-Reply-To: <5360.11799.qm@web50303.mail.re2.yahoo.com>
You need the AMD64 Application Binary Interface (v0.99) available at
http://www.x86-64.org/documentation.html
In particular, see Figure 3.4 on page 21.
Pay attention to the use of rax. The default for floating point in
x88-64 is the SSE unit. If a function will accept floating point
arguments (for example, printf) the number of floating point arguments
must be placed in eax. Write a C program that calls printf and use the
-S option to see the assembly language.
A good way to see what the compiler is doing to C code is to use the
following options:
$ gcc -O0 -g -Wa,-adhls -fno-asynchronous-unwind-tables \
> myProg.c > myProg.lst
(I added the "\" here to avoid confusing word wrapping.)
Bob
On Thu, 2008-12-04 at 12:20 -0800, £ukasz wrote:
> 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
next prev parent reply other threads:[~2008-12-04 20:54 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 [this message]
2008-12-04 20:55 ` Frederic Marmond
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=1228424058.5690.31.camel@bob-desktop \
--to=plantz@sonoma.edu \
--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 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).