common-lisp/sbcl.sbcl
1
0
Fork 0
mirror of git://git.code.sf.net/p/sbcl/sbcl synced 2026-09-10 07:26:40 -04:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

fix ffi documentation at the source

Browse source 
The generated texinfo files (e.g. ffi.texinfo) are under version
control only to be able to conveniently track the Markdown-to-Texinfo
output until it's deemed stable enough.
This commit is contained in:
Gabor Melis 2026-08-15 17:50:15 +02:00
parent f832c8e48e
commit a797aedf9d
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/manual/ffi.texinfo
View file

@ -775,9 +775,9 @@ call the function (as though it was declared with a prototype). The
type need not be known at compile time, but only known-type calls
are efficiently compiled.
On x86-64 and ARM64 systems, structures may be passed and returned by
value. The implementation follows the System V AMD64/Microsoft x64 and
AAPCS64 specifications respectively.
On x86-64 and ARM64 systems, structures may be passed and returned
by value. The implementation follows the System V AMD64 / Microsoft
x64 and AAPCS64 specifications, respectively.
Here is an example which allocates a @code{(struct foo)}, calls a foreign
function to initialize it, then returns a Lisp vector of all

6
src/code/target-alieneval.lisp
View file

@ -826,9 +826,9 @@ null byte."
type need not be known at compile time, but only known-type calls
are efficiently compiled.
On Unix-like x86-64 and ARM64 systems, structures may be passed and
returned by value. The implementation follows the System V AMD64 ABI
and AAPCS64 specifications respectively.
On x86-64 and ARM64 systems, structures may be passed and returned
by value. The implementation follows the System V AMD64 / Microsoft
x64 and AAPCS64 specifications, respectively.
Here is an example which allocates a `(STRUCT FOO)`, calls a foreign
function to initialize it, then returns a Lisp vector of all