This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: libffi-3.0.9 ported to OpenVMS IA64
- From: "Peter O'Gorman" <libffi-discuss at mlists dot thewrittenword dot com>
- To: Philippe Vouters <Philippe dot Vouters at laposte dot net>
- Cc: libffi-discuss at sourceware dot org
- Date: Sun, 6 Jun 2010 12:35:29 -0500
- Subject: Re: libffi-3.0.9 ported to OpenVMS IA64
- References: <1275346294.3132.529.camel@victor.vouters.dyndns.org>
On Tue, Jun 01, 2010 at 12:51:34AM +0200, Philippe Vouters wrote:
> Dear libffi reader,
>
> I ported your latest libffi-3.0.9 source code onto OpenVMS IA64 V8.3 for
> use by CPython VMS IA64. The libffi code passed all ctypes.test tests.
> For use by Java/JNA, some more libffi routine symbols may have to be
> added to libffi-3_0_9/libffi.opt.
>
> As Python does not support long doubles, this specific data type has not
> been tested although the code is ready for. I made code changes, mainly
> in ffi.c and unix.S_vms_ia64. As far as it looks the IA64 gcc compiler
> is much more permissive on type casting than the HP C for OpenVMS
> compiler is, explaining you the two assembly routines stf_spill and
> ldf_fill assembly code routines.
>
> For more information, refer to:
> http://vouters.dyndns.org/tima/OpenVMS-Python-ctypes-libffi-Python_module_ctypes.html
> where you can grab the source code from (in zipped OpenVMS backup
> format).
Hi,
Thanks for going to the effort of doing this!
The http://vouters.dyndns.org/zip/libffi-3.0.9.zip file linked on that
page says "You don't have permission to access /zip/libffi-3.0.9.zip on
this server.".
Why not provide diffs, then anyone on any OS can see what was changed?
Peter
--
Peter O'Gorman
pogma@thewrittenword.com