Mercurial > pub > dyncall > dyncall
diff doc/manual/callconvs/callconv_ppc32.tex @ 123:d203ba52c246
- manual callconv clarifications
author | cslag |
---|---|
date | Mon, 04 Jul 2016 16:13:59 +0200 |
parents | 9e99918065e6 |
children | f1fc1c836baf |
line wrap: on
line diff
--- a/doc/manual/callconvs/callconv_ppc32.tex Mon Jul 04 01:11:08 2016 +0200 +++ b/doc/manual/callconvs/callconv_ppc32.tex Mon Jul 04 16:13:59 2016 +0200 @@ -86,10 +86,10 @@ as defined for ellipsis calls) \item all nonvector parameters are aligned on 4-byte boundaries \item vector parameters are aligned on 16-byte boundaries -\item integer parameters \textless\ 32 bit occupy high-order bytes of their 4-byte area \item composite parameters with size of 1 or 2 bytes occupy low-order bytes of their 4-byte area. INCONSISTENT with other 32-bit PPC binary interfaces. In AIX and OS 9, padding bytes always follow the data structure \item composite parameters 3 bytes or larger in size occupy high-order bytes +\item integer parameters \textless\ 32 bit are right-justified (meaning occupy higher-address bytes) in their 4-byte area, requiring extra-care for big-endian targets \end{itemize} @@ -198,7 +198,7 @@ 32-bit general purpose registers (an odd and an even e.g. r3 and r4), probably skipping an even integer register. or passed on the stack. They are never splitted into a register and stack part. \item Ellipse calls set CR bit 6 - +\item integer parameters \textless\ 32 bit are right-justified (meaning occupy high-order bytes) in their 4-byte area, requiring extra-care for big-endian targets \end{itemize} \paragraph{Return values}