From: Philippe Vouters <Philippe.Vouters@laposte.net>
To: libffi-discuss@sourceware.org
Subject: libffi-3.0.9 ported to OpenVMS IA64
Date: Mon, 31 May 2010 22:51:00 -0000 [thread overview]
Message-ID: <1275346294.3132.529.camel@victor.vouters.dyndns.org> (raw)
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).
--
sip:Vouters.Philippe@ekiga.net
IM: philvout (Yahoo!)
http://vouters.dyndns.org/
Philippe Vouters (Fontainebleau/France)
next reply other threads:[~2010-05-31 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 22:51 Philippe Vouters [this message]
2010-06-06 17:35 ` Peter O'Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1275346294.3132.529.camel@victor.vouters.dyndns.org \
--to=philippe.vouters@laposte.net \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).