Mercurial > pub > dyncall > dyncall
comparison doc/manual/callconvs/callconv_mips64.tex @ 139:5675d34f0a06
- mips64 doc about impl status
- some more verbose output for one test
author | cslag |
---|---|
date | Mon, 08 Aug 2016 11:54:27 +0200 |
parents | f1fc1c836baf |
children | e210193f6cf1 |
comparison
equal
deleted
inserted
replaced
138:1b0c02e827c4 | 139:5675d34f0a06 |
---|---|
27 The word size is defined to be 32 bits, a dword 64 bits. Note that this is due to historical reasons (terminology didn't change from MIPS32).\\ | 27 The word size is defined to be 32 bits, a dword 64 bits. Note that this is due to historical reasons (terminology didn't change from MIPS32).\\ |
28 Other than that there are 64-bit versions of the other ABIs found for MIPS32, e.g. the EABI\cite{MIPSeabi} and O64\cite{MIPSo64}. | 28 Other than that there are 64-bit versions of the other ABIs found for MIPS32, e.g. the EABI\cite{MIPSeabi} and O64\cite{MIPSo64}. |
29 | 29 |
30 \paragraph{\product{dyncall} support} | 30 \paragraph{\product{dyncall} support} |
31 | 31 |
32 For MIPS 64-bit machines, dyncall supports the N32 and N64 calling conventions for calls and callbacks. | 32 For MIPS 64-bit machines, dyncall supports the N64 calling conventions for calls and callbacks (for big- and little-endian targets). |
33 Our test machine is a Loongson-CPU 2F subnotebook, as well as an EdgeRouter Lite, both running OpenBSD. | 33 The N32 calling convention might work - it used to, but hasn't been tested, recently. |
34 | 34 |
35 \subsubsection{MIPS N64 Calling Convention} | 35 \subsubsection{MIPS N64 Calling Convention} |
36 | 36 |
37 \paragraph{Register usage} | 37 \paragraph{Register usage} |
38 | 38 |