4 libffi-3.0.10 was released on XXXXXXXXXX, 2010. Check the libffi web
5 page for updates: <URL:http://sourceware.org/libffi/>.
11 Compilers for high level languages generate code that follow certain
12 conventions. These conventions are necessary, in part, for separate
13 compilation to work. One such convention is the "calling
14 convention". The "calling convention" is essentially a set of
15 assumptions made by the compiler about where function arguments will
16 be found on entry to a function. A "calling convention" also specifies
17 where the return value for a function is found.
19 Some programs may not know at the time of compilation what arguments
20 are to be passed to a function. For instance, an interpreter may be
21 told at run-time about the number and types of arguments used to call
22 a given function. Libffi can be used in such programs to provide a
23 bridge from the interpreter program to compiled code.
25 The libffi library provides a portable, high level programming
26 interface to various calling conventions. This allows a programmer to
27 call any function specified by a call interface description at run
30 FFI stands for Foreign Function Interface. A foreign function
31 interface is the popular name for the interface that allows code
32 written in one language to call code written in another language. The
33 libffi library really only provides the lowest, machine dependent
34 layer of a fully featured foreign function interface. A layer must
35 exist above libffi that handles type conversions for values passed
36 between the two languages.
42 Libffi has been ported to many different platforms.
43 For specific configuration details and testing status, please
44 refer to the wiki page here:
46 http://www.moxielogic.org/wiki/index.php?title=Libffi_3.0.10
48 At the time of release, the following basic configurations have been
51 |--------------+------------------|
52 | Architecture | Operating System |
53 |--------------+------------------|
80 | X86 | Windows/Cygwin |
81 | X86 | Windows/MingW |
85 | X86-64 | Windows/MingW |
86 |--------------+------------------|
88 Please send additional platform test results to
89 libffi-discuss@sourceware.org and feel free to update the wiki page
95 First you must configure the distribution for your particular
96 system. Go to the directory you wish to build libffi in and run the
97 "configure" program found in the root directory of the libffi source
100 You may want to tell configure where to install the libffi library and
101 header files. To do that, use the --prefix configure switch. Libffi
102 will install under /usr/local by default.
104 If you want to enable extra run-time debugging checks use the the
105 --enable-debug configure switch. This is useful when your program dies
106 mysteriously while using libffi.
108 Another useful configure switch is --enable-purify-safety. Using this
109 will add some extra code which will suppress certain warnings when you
110 are using Purify with libffi. Only use this switch when using
111 Purify, as it will slow down the library.
113 It's also possible to build libffi on Windows platforms with
114 Microsoft's Visual C++ compiler. In this case, use the msvcc.sh
115 wrapper script during configuration like so:
117 path/to/configure CC=path/to/msvcc.sh LD=link CPP=\"cl -nologo -EP\"
119 For 64-bit Windows builds, use CC="path/to/msvcc.sh -m64".
120 You may also need to specify --build appropriately. When building with MSVC
121 under a MingW environment, you may need to remove the line in configure
122 that sets 'fix_srcfile_path' to a 'cygpath' command. ('cygpath' is not
123 present in MingW, and is not required when using MingW-style paths.)
125 Configure has many other options. Use "configure --help" to see them all.
127 Once configure has finished, type "make". Note that you must be using
128 GNU make. You can ftp GNU make from prep.ai.mit.edu:/pub/gnu.
130 To ensure that libffi is working as advertised, type "make check".
131 This will require that you have DejaGNU installed.
133 To install the library and header files, type "make install".
139 See the ChangeLog files for details.
142 Fix the N64 build on mips-sgi-irix6.5.
143 Testsuite fixes for Tru64 Unix.
144 Enable builds with Microsoft's compiler.
145 Enable x86 builds with Sun's compiler.
148 Add AVR32 and win64 ports. Add ARM softfp support.
149 Many fixes for AIX, Solaris, HP-UX, *BSD.
150 Several PowerPC and x86-64 bug fixes.
151 Build DLL for windows.
154 Add *BSD, BeOS, and PA-Linux support.
158 (thanks to Andreas Tobler)
161 Fix for closures on sh.
162 Mark the sh/sh64 stack as non-executable.
163 (both thanks to Kaz Kojima)
167 Fix #define ARM for IcedTea users.
171 Fix x86 OpenBSD configury.
174 Enable x86 OpenBSD thanks to Thomas Heller, and
175 x86-64 FreeBSD thanks to Björn König and Andreas Tobler.
176 Clean up test instruction in README.
179 Improved x86 FreeBSD support.
180 Thanks to Björn König.
183 Fix instruction cache flushing bug on MIPS.
184 Thanks to David Daney.
187 Many changes, mostly thanks to the GCC project.
188 Cygnus Solutions is now Red Hat.
193 Raffaele Sena produces ARM port.
196 Fixed x86 long double and long long return support.
197 m68k bug fixes from Andreas Schwab.
198 Patch for DU assembler compatibility for the Alpha from Richard
202 Bug fixes and MIPS configuration changes.
205 Bug fixes and m68k port from Andreas Schwab. PowerPC port from
206 Geoffrey Keating. Various bug x86, Sparc and MIPS bug fixes.
209 Richard Henderson produces Alpha port.
212 Fixed an n32 ABI bug. New libtool, auto* support.
215 libtool is now used to generate shared and static libraries.
216 Fixed a minor portability problem reported by Russ McManus
220 Added --enable-purify-safety to keep Purify from complaining
221 about certain low level code.
222 Sparc fix for calling functions with < 6 args.
226 Added missing ffi_type_void, needed for supporting void return
227 types. Fixed test case for non MIPS machines. Cygnus Support
228 is now Cygnus Solutions.
231 Added notes about GNU make.
234 Added configuration fix for non GNU compilers.
237 Added --enable-debug configure switch. Clean-ups based on LCLint
238 feedback. ffi_mips.h is always installed. Many configuration
239 fixes. Fixed ffitest.c for sparc builds.
242 Fixed n32 problem. Many clean-ups.
245 Gordon Irlam rewrites v8.S again. Bug fixes.
248 Gordon Irlam improved the sparc port.
251 Interface changes based on feedback.
254 Sparc port complete (modulo struct passing bug).
257 Passing struct args, and returning struct values works for
258 all architectures/calling conventions. Expanded tests.
261 Added SGI n32 support. Fixed bugs in both o32 and Linux support.
265 Fixed float passing bug in mips version. Restructured some
266 of the code. Builds cleanly with SGI tools.
269 First release. No public announcement.
275 libffi was originally written by Anthony Green <green@redhat.com>.
277 The developers of the GNU Compiler Collection project have made
278 innumerable valuable contributions. See the ChangeLog file for
281 Some of the ideas behind libffi were inspired by Gianni Mariani's free
282 gencall library for Silicon Graphics machines.
284 The closure mechanism was designed and implemented by Kresten Krab
287 Major processor architecture ports were contributed by the following
290 alpha Richard Henderson
292 cris Simon Posnjak, Hans-Peter Nilsson
297 mips Anthony Green, Casey Marshall
299 pa Randolph Chung, Dave Anglin, Andreas Tobler
300 powerpc Geoffrey Keating, Andreas Tobler,
301 David Edelsohn, John Hornkvist
302 powerpc64 Jakub Jelinek
303 s390 Gerhard Tonn, Ulrich Weigand
306 sparc Anthony Green, Gordon Irlam
307 x86 Anthony Green, Jon Beniston
310 Jesper Skov and Andrew Haley both did more than their fair share of
311 stepping through the code and tracking down bugs.
313 Thanks also to Tom Tromey for bug fixes, documentation and
316 Thanks to Jim Blandy, who provided some useful feedback on the libffi
319 Andreas Tobler has done a tremendous amount of work on the testsuite.
321 Alex Oliva solved the executable page problem for SElinux.
323 The list above is almost certainly incomplete and inaccurate. I'm
324 happy to make corrections or additions upon request.
326 If you have a problem, or have found a bug, please send a note to