This is the mail archive of the
mailing list for the libffi project.
Re: libffi - the 10th Anniversary Release
- From: Thomas Heller <theller at ctypes dot org>
- To: libffi-discuss at sourceware dot org
- Cc: Dalibor Topic <robilad at kaffe dot org>, Tom Tromey <tromey at redhat dot com>, Anthony Green <green at redhat dot com>, theller at python dot net
- Date: Tue, 29 Jan 2008 20:12:47 +0100
- Subject: Re: libffi - the 10th Anniversary Release
- References: <479F1FCB.firstname.lastname@example.org> <email@example.com> <479F4C46.firstname.lastname@example.org>
Dalibor Topic schrieb:
> Tom Tromey wrote:
>> Dalibor also pointed out this patch:
>> This adds Win64 support.
> As ctypes is theller's code, and he seems to have a bunch of different
> libffi patches stuck away in branches,
> I figured it's best to ping theller himself what to merge. I'd love to
> see the arm-wince stuff go in, but I have
> nothing to test it myself.
Well, the libffi_msvc directory is a branch of the libffi sources, adapted
so that they can be compiled with the MS compilers. Both for win32/x86 and
win64/amd64. Both the cdecl and stdcall calling conventions are supported,
also for closures. The ffi_call function has been changed to return an integer
which informs about the stack pointer difference before and after the function call;
this is to detect wrong calling convention or wrong number of parameters passed (in stdcall).
The libffi_asm_wince directory is for MS compilers and windows ce/arm, with
The changes to the libffi directory that I remember are these:
- New configure system (this was not written by me). The goal was
to have no GPL'd files in the Python svn repo. Also the libffi sources
are not compiled into a shared library, instead they are linked into
the Python ctypes extension that uses it.
- We changed the libffi sources to use proper function prototypes
since we have a zero-compiler-warning policy. For example:
-extern void ffi_call_osf(void *, unsigned long, unsigned, void *, void (*)())
+extern void ffi_call_osf(void *, unsigned long, unsigned, void *, void (*)(void))
Is there a reason to keep these 'void (*)()' constructs?
- Remove live_support (for OS X 10.3, IIRC), as already mentioned:
- A fix for FreeBSD/x86:
- Add .note.GNU-stack to sysv.S so that ctypes isn't considered as requiring executable stacks.
The directories I mentioned above are all relative to
(for svn) http://svn.python.org/view/python/trunk/Modules/_ctypes/
(for viewcvs) http://svn.python.org/projects/python/trunk/Modules/_ctypes/