libffi-compat
a portable, high level programming interface to various calling conventions
Compilers for high level languages generate code that follow certain conventions. These conventions are necessary, in part, for separate compilation to work. One such convention is the "calling convention". The "calling convention" is essentially a set of assumptions made by the compiler about where function arguments will be found on entry to a function. A "calling convention" also specifies where the return value for a function is found. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. Libffi can be used in such programs to provide a bridge from the interpreter program to compiled code. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. Ffi stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The libffi library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above libffi that handles type conversions for values passed between the two languages.
homepage ↗ cpe: cpe:/a:libffi_project:libffi github: libffi/libffi
Available in
| Overlay | Newest | Ebuilds | Last activity | |
|---|---|---|---|---|
| gentoo gitweb ↗ | 3.3-r2 | 2 | 17 h | details › |
Versions & arches
| Version | Overlay | amd64 | arm64 | x86 | ppc64 | riscv | alpha | arm | hppa | m68k | ppc | s390 | sparc | x64-macos | x64-solaris | Committed | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 3.3-r2 | gentoo | amd64 stable | arm64 testing | x86 stable | ppc64 testing | riscv testing | alpha testing | arm testing | hppa testing | m68k testing | ppc testing | s390 testing | sparc testing | x64-macos testing | x64-solaris testing | — | view · download · history ↗ |
| 3.2.1-r3 | gentoo | amd64 stable | arm64 testing | x86 stable | ppc64 testing | riscv untested | alpha testing | arm testing | hppa testing | m68k testing | ppc testing | s390 testing | sparc testing | x64-macos testing | x64-solaris testing | — | view · download · history ↗ |
Use flags of 3.3-r2
- debug Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
- pax-kernel Use PaX emulated trampolines, for we can't use PROT_EXEC
- test Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
8 expansion flags (python targets, ABIs, cpu flags…)
- abi_x86_32
- abi_x86_64
- abi_x86_x32
- abi_mips_n32
- abi_mips_n64
- abi_mips_o32
- abi_s390_32
- abi_s390_64