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

[cffi-devel] Latest changes, (probably) no significant errors with CFFI
by Juan Jose Garcia-Ripoll 27 Apr '10

27 Apr '10

I have fixed one more bug in ECL, this time related to the alignment of elementary C types (double, int, etc). We now gather the information from the compiler at compilation time, which is great, portable and robust. With this fix CFFI, plus the patches I submitted for the CFFI test suite, ECL has no unexpected failure and the output of the test suite is 4 out of 222 total tests failed: DEFCFUN.NOOP, CALLBACKS.BFF.1, CALLBACKS.BFF.2, STRING.ENCODINGS.ALL.BASIC. There remain two question. The simplest one is as follows: does it make sense to provide inline forms for %foreign-type-size and %foreign-type-alignment, or are they use scarcely? The second question is whether CFFI itself produces inline forms of the expressions dealing with foreign types. I mean conversion to/from lisp, etc. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

1 0

[cffi-devel] Status of CFFI-ECL port
by Juan Jose Garcia-Ripoll 26 Apr '10

26 Apr '10

If we include the fix for the test suite and use the latest changes I incorporated to ECL's git tree, the current status is that there are still 6 unexpected failures 10 out of 222 total tests failed: DEFCFUN.NOOP, CALLBACKS.BFF.1, CALLBACKS.BFF.2, STRING.ENCODINGS.ALL.BASIC, STRUCT.ALIGNMENT.3, STRUCT.ALIGNMENT.4, STRUCT.ALIGNMENT.5, STRUCT.ALIGNMENT.6, STRUCT.ALIGNMENT.7, STRUCT.ALIGNMENT.8. 6 unexpected failures: STRUCT.ALIGNMENT.3, STRUCT.ALIGNMENT.4, STRUCT.ALIGNMENT.5, STRUCT.ALIGNMENT.6, STRUCT.ALIGNMENT.7, STRUCT.ALIGNMENT.8. I hope I will be able to fix them in the coming days. Any hints / help are appreciated. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

1 0

[cffi-devel] New patches: 25-Apr-2010
by Luis Oliveira 26 Apr '10

26 Apr '10

Sun Apr 25 19:12:32 EDT 2010 Luis Oliveira <loliveira(a)common-lisp.net> * cffi-ecl: simplify shareable vector implementation Patch courtesy of Juan Jose Garcia-Ripoll. M ./src/cffi-ecl.lisp -28 +1 Sun Apr 25 19:02:19 EDT 2010 Luis Oliveira <loliveira(a)common-lisp.net> * cffi-ecl: inline %mem-set and %mem-ref Patch courtesy of Juan Jose Garcia-Ripoll. M ./src/cffi-ecl.lisp -17 +49 M ./tests/memory.lisp +5 Sun Apr 25 18:50:04 EDT 2010 Luis Oliveira <loliveira(a)common-lisp.net> * cffi-ecl: use C-INLINE when producing compiled code Using the ECL extension EXT:WITH-BACKEND, CFFI can produce code that works differently when using the interpreter than when using the lisp2C compiler. This leads to more efficient code. This change is backwards compatible. Patch courtesy of Juan Jose Garcia-Ripoll. M ./src/cffi-ecl.lisp -22 +41 Sun Apr 25 18:39:14 EDT 2010 Luis Oliveira <loliveira(a)common-lisp.net> * cffi-ecl: reexport NULL-POINTER-P from SI Patch courtesy of Juan Jose Garcia-Ripoll. M ./src/cffi-ecl.lisp -4 +1 Sun Apr 25 18:37:48 EDT 2010 Luis Oliveira <loliveira(a)common-lisp.net> * cffi-ecl: use ECL's :long-long feature Patch courtesy of Juan Jose Garcia-Ripoll. M ./src/cffi-ecl.lisp -3 +5 Sun Apr 25 08:24:43 EDT 2010 Luis Oliveira <loliveira(a)common-lisp.net> * Allegro: fix WITH-FOREIGN-POINTER - Fixes previous patch. - New test: WITH-FOREIGN-POINTER.CONSTANT-SIZE. M ./src/cffi-allegro.lisp -2 +2 M ./tests/memory.lisp -2 +11 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-100425.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi-cffi;a=summary

1 0

[cffi-devel] Updating ECL's implementation of shareable vectors
by Juan Jose Garcia-Ripoll 25 Apr '10

25 Apr '10

ECL already provides a function to get a pointer associated to an array. CFFI should use it. Patch attached. -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

2 1

Re: [cffi-devel] %mem-{set,ref} can be inlined?
by Luís Oliveira 25 Apr '10

25 Apr '10

On Sun, Apr 25, 2010 at 5:49 PM, Juan Jose Garcia-Ripoll <juanjose.garciaripoll(a)googlemail.com> wrote: > Ok, if this is the case then here is a slightly simpler patch. [...] > Could you add it to the test suite, just in case? Pushed your patch, along with the test. Thanks. -- Luís Oliveira http://r42.eu/~luis/

1 0

[cffi-devel] %mem-{set,ref} can be inlined?
by Juan Jose Garcia-Ripoll 25 Apr '10

25 Apr '10

I had a look at the definitions of these two functions. Right now in cffi-ecl.lisp it seems that they are only called with basic types, for they call cffi-type->ecl-type which only deals with things like integers, doubles, etc. Could I just produce a compiler macro that relies on this? The result would be much much simpler than this as it could be inlined and make use of ECL's embedded C statements. Actually it would be nice if instead of a compiler macro I could define them to be just plain macros. Anything that prevents it? Juanjo (defun %mem-ref (ptr type &optional (offset 0)) "Dereference an object of TYPE at OFFSET bytes from PTR." (let* ((type (cffi-type->ecl-type type)) (type-size (ffi:size-of-foreign-type type))) (si:foreign-data-ref-elt (si:foreign-data-recast ptr (+ offset type-size) :void) offset type))) -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

2 3

[cffi-devel] Strange equivalence
by Juan Jose Garcia-Ripoll 25 Apr '10

25 Apr '10

In the file cffi-ecl.lisp of I find the equivalence table (:char :byte "char") (:unsigned-char :unsigned-byte "unsigned char") that associates, for the ECL port, a byte with the CFFI :char type. Is this intended per-specification? Why not using ECL's :char type, which might be more than one byte if the compiler and operating system expect so? Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

2 1

[cffi-devel] Not able to use constant variables in with-foreign-pointer
by Jianshi Huang 25 Apr '10

25 Apr '10

Hi, There's a minor problem in the cffi-allegro.lisp that prevents using constant variables in with-foreign-pointer. Would you please apply the patch? Tue Apr 20 19:16:26 JST 2010 Jianshi Huang <huang(a)msi.co.jp> * Fix bug that size in with-foreign-pointer cannot be a constant variable. diff -rN old-cffi/src/cffi-allegro.lisp new-cffi/src/cffi-allegro.lisp 139c139 < (ff:with-static-fobject (,var '(:array :char ,size) --- > (ff:with-static-fobject (,var (list :array :char ,size) Cheers, Jianshi

3 3

[cffi-devel] New patches: 21-Apr-2010
by Luis Oliveira 22 Apr '10

22 Apr '10

Wed Apr 21 05:19:56 EDT 2010 Jianshi Huang <huang(a)msi.co.jp> * Allow the use of constants in WITH-FOREIGN-OBJECT for Allegro. M ./src/cffi-allegro.lisp -1 +1 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-100421.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi-cffi;a=summary

1 0

[cffi-devel] About double pointers and C & operator
by Alexandre Paes 19 Apr '10

19 Apr '10

Hi, For a test project, i was creating a CFFI interface to the OpenCV library and my limited knowledge of CFFI has left me wondering how to achieve something. According to the documentation on the OpenCV wiki, in order to start capturing from a webcam one would call the following function: CvCapture* cvCreateCameraCapture (int index) The CvCapture is an opaque structure without public interface, so i simply store the pointer returned by the function. To end the image capturing, one would release the capture through the function: void cvReleaseCapture(CvCapture** capture) On the OpenCV wiki there is a sample program ( http://opencv.willowgarage.com/wiki/CameraCapture) that basically has: int main() { ... CvCapture* capture = cvCaptureFromCAM( CV_CAP_ANY ); ... cvReleaseCapture( &capture ); ... } I've defined the foreign functions as: (cffi:defcfun ("cvCreateCameraCapture" create-camera-capture) :pointer (index :int)) (cffi:defcfun ("cvReleaseCapture" %release-capture) :void (capture :pointer)) Then in my program i call 'create-camera-capture and it works, the webcam lights up and starts capturing. I even managed to simulate the &capture behavior by renaming the previous declaration of release-capture to %release-capture and creating a new definition like: (defun release-capture (capture*) (cffi:with-foreign-object (capture** :long) (setf (cffi:mem-ref capture** :long) (cffi:pointer-address capture*)) (%release-capture capture**))) It works but it doesn't feel all that nice, is this the best/correct way of achieving the same as the C code? Cheers, Alex Paes

2 1