April 2011 - cffi-devel - mailman3.common-lisp.net

[cffi-devel] Digitool MCL support for CFFI (was Re: [info-mcl] ? cffi)
by Chun Tian (binghe) 10 Mar '12

10 Mar '12

Hi, CFFI developers Digitool MCL was a old&famous Common Lisp implementation on PPC Mac OS. Recently it was ported into Intel Mac OS X by running in Rosetta (a PPC emulator by Apple). So there're people still using this platform even when Clozure CL is a better choice. Attach is two patches, one is a CFFI MCL support patch made by James Anderson, the other is a trivial patch for MCL support of trivial-features made by me. With these two patch, CFFI can now be loaded into Digitool MCL. This work seems work with James' own project which is based on CFFI. But CFFI-TESTS cannot run at this time, because ASDF:RUN-SHELL-COMMAND doesn't support MCL (I don't know how to fix this right now). IOlib also cannot work in MCL because Gray Streams wasn't supported by MCL yet ... However, I hope CFFI maintainer could merge this patch and let other MCL users help improving exist work. Chun Tian (binghe) 在 2010-9-28，06:41， james anderson 写道： > good morning; > > i have worked out enough of a cffi-mcl to be able to accomplish the immediate goal - to use the cl-zmq zeromq ffi binding.[1] > in case someone wants to carry it further, it's posted along with a mcl-compatible zmq version,[2] which eliminates un-ported dependencies. > > --- > [1] : http://repo.or.cz/w/cl-zmq.git > [2] : http://github.com/lisp/de.setf.zeromq > > On 2010-09-22, at 08:29 , Chun Tian (binghe) wrote: > >> I've read these documents. MCL 4.0's FFI seems based on the function "define-entry-point" which then depends on "ppc-ff-call", both of them are still available in MCL 5.x, and the related MCL source code is "lib/deftrap.lisp", which was last modified in 2005. >> >> However, I think "define-entry-point" is not the preferred way any more: >> >> ; Change log >> ; >> ; put back define-entry-point and things it depends on - though MCL doesn't use it users may >> ; ------ 5.2b2 >> >> I think CFFI people, if want to support MCL, should research "deftrap.lisp" and figure out the preferred way to do the work. But for me, a USOCKET maintainer, I'd like to use this interface directly to implement UDP networking, which was lack from OpenTransport. >> >> --binghe >> >> 在 2010-9-22，13:30， james anderson 写道： >> >>> there are two sources. >>> >>> if you go to ftp.clozure.com, you will find the 5.2 release and a copy of the documentation for 4.0. >>> i know of no revised documentation for 5.2. other than that, there is always the source. >>> i believe 5.2 has a very different calling mechanism then 4.0, as it uses a different os x facility to manage foreign libraries. >>> >>> the biggest '?' is turning off the gc for the dynamic extent of any foreign calls which pass lisp data. i do not know if that is possible in mcl, but it could be faked by moving the data to/from temporary external storage just to get it working. >>> two little question marks are the data type size calculations and the call-back protocol. >>> since the source is there, there's nothing stopping me from adapting the clozure-specific code to work in mcl. >>> i was just hoping to avoid having to wrap my head around those bits. >>> >>> >>> On 2010-09-22, at 04:45 , Chun Tian (binghe) wrote: >>> >>>> Never know how to do FFI in Digitool MCL ... Where can I find some API documents? >>>> >>>> --binghe >>>> >>>> 在 2010-9-22，05:36， james anderson 写道： >>>> >>>>> good morning; >>>>> >>>>> has anyone ported cffi to mcl? >>>>> >>>>> >>>>> _______________________________________________ >>>>> info-mcl mailing list >>>>> info-mcl(a)clozure.com >>>>> http://clozure.com/mailman/listinfo/info-mcl >>>> >>>> _______________________________________________ >>>> info-mcl mailing list >>>> info-mcl(a)clozure.com >>>> http://clozure.com/mailman/listinfo/info-mcl >>> >>> _______________________________________________ >>> info-mcl mailing list >>> info-mcl(a)clozure.com >>> http://clozure.com/mailman/listinfo/info-mcl >> >> _______________________________________________ >> info-mcl mailing list >> info-mcl(a)clozure.com >> http://clozure.com/mailman/listinfo/info-mcl > > _______________________________________________ > info-mcl mailing list > info-mcl(a)clozure.com > http://clozure.com/mailman/listinfo/info-mcl

2 3

[cffi-devel] HDF5 bindings
by Daniel Herring 20 May '11

20 May '11

Hi all, I've made good progress on binding the HDF5 file format library. HDF5 is an efficient, self-describing, extensible, binary file format that is popular in scientific computing, underlies NetCDF, is used by petabytes of data, is supported by tools like Matlab, ... http://www.hdfgroup.org/HDF5/whatishdf5.html My bindings are not quite ready for general consumption by the average CL user, but they should be quite usable by a CFFI programmer. The sources are here: https://gitorious.org/dh-misc/hdf5 Please read the README.txt first. As always, help would be appreciated, and the usual disclaimers of "this software may munge your data" apply. Later, Daniel

2 1

[cffi-devel] test failures with acl/windows
by Anton Vodonosov 21 Apr '11

21 Apr '11

Hello. For your information. I've just run the cffi-0.10.6 tests on Allegro 8.2 express edition on Windows. There are failures. I have impression that these failures make CFFI non working even in quite simple and straightforward foreign library interactions from ACL/Windows (I experimented a little in this direction). The full test output is attached. Best regards, - Anton

1 1

[cffi-devel] introspection in cffi
by nitralime 14 Apr '11

14 Apr '11

/*Hi folks!*/ Is there a way to get the (meta) information of structure slots defined by */defcstruct/*? Consider the following concrete example: (defcstruct test (a :uint) (b :char :count 10) (c :pointer)) Is it possible to get info like type, (array-)size of the slots /*a, b* /and /*c*/ by only introspecting '/*test*/'? Something like (foreign-slot-type 'test 'a) /*==> :char*/ (foreign-slot-count 'test 'b) /*==> 10*/ would be very useful! Regards Nik

2 1

[cffi-devel] CCL on Windows errors
by Anton Vodonosov 12 Apr '11

12 Apr '11

Hello. I have a crash when use CFFI + CCL + callbacks on Windows. I am not sure the crash is caused by CFFI, there is another suspect. But the CFFI tests on Windows have errors. Could you take a look to the test results (attached)? This is CFFI 0.10.6 About the crash. It happens with CL+SSL. OpenSSL requires multi-threaded applications to provide a callback, which implements locking, as described here: http://www.openssl.org/docs/crypto/threads.html. The callback function prototype is void locking_function(int mode, int n, const char *file, int line) The callback is installed using void CRYPTO_set_locking_callback(void (*func)(int mode,int type, const char *file,int line)) CL+SSL has the following definitions: (cffi:defcallback locking-callback :void ((mode :int) (n :int) (file :string) (line :int)) ;(declare (ignore file line)) ;; the callback body here ) (cffi:defcfun ("CRYPTO_set_locking_callback" crypto-set-locking-callback) :void (fun :pointer)) If during initialization of CL+SSL we do (crypto-set-locking-callback (cffi:callback locking-callback)) then we have a crash at the first SSL connection to hunchentoot. The crash is 100% reproducible. It doesn't matter what we have in the callback body, it may be even empty. The symptoms are always the same. If we comment out the line ;; (crypto-set-locking-callback (cffi:callback locking-callback)) then the crash doesn't happen. As I said, I am not sure CFFI is the cause of the crash. I tried to print the values passed to the callback, they are not corrupted, valid numbers and strings. Also, the callback is called thousands of times before the crash happen. But on the other hand, if we don't set the callback, the crash doesn't happen; and setting even empty callback guarantees the crash... Anyway, If you provide any patches to CFFI, at least to fix the tests, I can run the tests on Windows. Best regards, - Anton

2 4